Sass I'm confused

If I install sass with

sudo dnf install sass

An obsolute version of Sass (ruby-sass) gets installed. Uninstall with

sudo dnf remove sass

Gives an error “No packages to remove for argument: sass” . That’s odd, I though I just installed it. Uninstall with

sudo dnf remove rubygem-sass

seems to do the trick. which rises two questions:

  1. why isn’t the dnf install symetrical? I install and remove a package with the same name.
  2. why is ruby sass prefered in Fedora? Should this be dart-sass as ruby sass is depricated?

I think this is a downside of “dnf install” trying to be “smart” (or helpful). There is no package called “sass”, so it falls back to “what provides /usr/bin/sass, because that’s probably what the user wants”. But that same logic doesn’t work in the “dnf remove” command, so it’s asymmetric (you do get output from “dnf install” that tells you the package it installs is “rubygem-sass” though).

So the sass Ruby gem is not “preferred” in Fedora, this is just a quirk of how the package manager resolves the string “sass” on install. That said, I don’t think we can package the new Dart reference implementation, just … because it’s Dart, and we don’t have the Dart compiler / runtime available in Fedora (yet?).

There are other / newer SASS CSS / SCSS implementations that are available, though (sassc or grass). Many packages that need to compile CSS at build-time already prefer one of these over the old Ruby implementation.

2 Likes

Oh that makes sense and indeed the install showed the full qualified package name. However I –still– am able to memorize commands I type in, whatever output dnf install generates is wiped from short-time wetware memory pretty quickly.

I wonder why the peeps at sass-lang.com don’t mention sassc . (EDIT: sassc is a wrapper around libsass which is no longer maintained. )

(oh and there is not --watch on sassc…)

Ctrl-R in the terminal for those times when the wetware lets you down! :slight_smile:

I’m also paranoid. :smiley:

And the history command.

1 Like

With multiple terminals (nemo-terminal) I’ve found the history less than reliable. Sometimes commands are there sometimes not.

You can config for more reliable .bash_history contents.

In my ~/.bashrc I have this line

shopt -s histappend
1 Like