On Fri, Sep 16, 2022 at 1:14 AM Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote:
As I'm implementing this, I'm realizing that it probably only makes
sense to have the default version of Node.js on each Fedora release
provide the unversioned-command. Otherwise it becomes really hard to
ensure that the RPM macros like %{nodejs_sitelib} refer to the correct
location. So I think I'll stick with "if you're packaging for Fedora,
it has to work on the default Node release *or* you must deal with
everything yourself if you need to run on a different runtime".
Sounds reasonable (as a non-nodejs user:)
For our Haskell ghc, the new ghcX.Y packages introduced since F36 have given a big improvement in flexibility in my opinion.
The main Fedora ghc package provides /usr/bin/ghc by default, though the ghcX.Y packages do have an optional unversioned subpackage for it that conflicts with ghc.
So users are normally expected just to use the default version or specify the wanted version, unless they really want to default to a newer (or older in the future) one instead.
Jens
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
