Follow-up on the naming point raised earlier in this report.
The source package is now dart-sass, matching upstream's project and standalone
executable name, as suggested there. One source builds two binaries:
dart-sass the compiler as a self-contained native executable, installed as
/usr/bin/dart-sass; Architecture: amd64, and it needs neither the
Dart SDK nor Node.js at run time
node-sass the dart2js build as the Node.js module "sass", installed under
/usr/share/nodejs/sass for bundlers such as sass-loader;
Architecture: all
The generic command name is not claimed outright: the package provides the
virtual package "sass" and offers /usr/bin/sass, with its manual page as an
alternatives slave, through update-alternatives (priority 40), which is what
Policy 3.9 asks for so that implementations can be installed together. No
Conflicts/Replaces and no dpkg-divert are used. ruby-sass ships that path as a
plain file, so there the name stays with ruby-sass and our alternative is only
registered; ruby-sass is being asked separately to offer it as an alternative
too.
Packaging: https://salsa.debian.org/dart-team/dart-sass
