Description of problem: Can rubygem-sass be branched for EPEL8? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Generally, I am not interested in EPEL8, but I don't mind anybody else maintaining the package there. However, this is special case and I strongly suggest against importing this into EPEL, because this package is deprecated upstream [1] and it has been replaced by rubygem-sassc. [1] https://sass-lang.com/ruby-sass
Hi Pat, As you may know, the sass upstream project stopped maintaining it. https://github.com/sass/ruby-sass > Ruby Sass should no longer be used, and will no longer be receiving any updates. See the Sass blog, and consider switching to the sassc gem. You can see the alternatives in the blog. http://sass.logdown.com/posts/7828841
"Dart Sass" can be also the alternative.
(In reply to Jun Aruga from comment #3) > "Dart Sass" can be also the alternative. If someone can be bothered to package it.
Vit, what is the problem if we create "epel8" branch? What if Pat becomes co-maintainer of rubygem-sass even when you are not interested in it? If we do not have the alternative RPM on Fedora right now, and people want to use rubygem-sass RPM, it's worth to create it, isn't it? Though it's hard to fix an issue. Pat, how about installing sass directly from gem command? ``` $ gem install sass --user-instal -v X.Y.Z ```
(In reply to Jun Aruga from comment #5) > Vit, what is the problem if we create "epel8" branch? If there was some reasoning behind the initial request, we could discuss what is the proper way forward.
The 'mint-themes' package uses rubygem-sass for its build process. I'm looking into to other options for achieving the build.
Hm, there is no `sass` executable in rubygem-sassc. But something like [1] could be possibility. [1] https://github.com/sass/sassc-ruby#usage
FWIW, I happened to notice that the latest upstream version of python-webassets is also blocked on the dart sass implementation: https://bugzilla.redhat.com/show_bug.cgi?id=1785697#c2 the python-webassets code upstream has been adjusted to assume the dart implementation of /usr/bin/sass , but we still have the old rubygem implementation of it, so python-webassets is stuck on an old version.
I just requested the epel8 branch now. It does not mean I will maintain the branch regularly. I just will build it at once at least if someone needs it. ``` $ fedpkg request-branch --repo rubygem-sass epel8 https://pagure.io/releng/fedora-scm-requests/issue/25445 https://pagure.io/releng/fedora-scm-requests/issue/25446 ```
WIP: Initial package https://src.fedoraproject.org/rpms/rubygem-sass/pull-request/3 I share how to merge with squash for epel8 branch, as it's useful for other packages epel8 cases. ``` $ git pull $ git checkout epel8 $ git checkout -b wip/epel8 $ git merge --squash --no-commit master $ rpmdev-bumpspec rubygem-sass.spec ``` Rebase modifying the changelog part and release number. ``` $ fedpkg --release epel8 srpm $ mock -r epel-8-x86_64 *.rpm ... No matching package to install: 'rubygem(listen)' ... ``` rubygem-listen epel8 is necessary to build rubygem-sass on epel8.