Hello list! Cross-posting here from the discussion [1] on the Changes/NodeJSMetapackages [2] proposal, for people who read mailing lists, but not Fedora discussion. Feel free to respond in either place.
[1]: https://discussion.fedoraproject.org/t/f43-change-proposal-nodejs-metapackage-self-contained/157322/9 [2]: https://fedoraproject.org/wiki/Changes/NodeJSMetapackages --- Hello, another update from the team! The implementation progresses, and barring few issues to still be ironed out, it looks like it could be merged to the rawhide soon™. With this comes the necessary task of determining the upgrade path for the current `nodejs22` users. (`nodejs22` is currently the “default” stream in both Fedora 44 and Rawhide.) Somewhat unfortunate side-effect of rolling out the -bin packages change separately from this one is that we cannot tell whether the user used `dnf install nodejs` or `dnf install nodejs22` to obtain the respective packages; all we can tell is that the `nodejs22` package is installed on the system. This means that with moving to the metapackage approach, we will need to break one of the promises we are making: 1. If you use `dnf install nodejs`, you will be upgraded across distributions when appropriate. 2. If you use `dnf install nodejs22`, it won’t be touched unless you `dnf swap` to something else. So the question is what would be less disruptive: 1. Treat `nodejs22` as being the default-stream, upgrading it to the new `nodejs` rolling stream and possibly to nodejs v24 in Rawhide/F45. This would match what would happen before we started to experiment with all these changes, but will make people that specifically wanted to have nodejs v22 unhappy. 2. Treat `nodejs22` as being the specific stream, just provide the new packages and do nothing else. This will make unhappy the people who did `dnf install nodejs` one time and expect to be kept on supported version even across system upgrades (which includes those who just installed nodejs and then forgot about it). Note that in both cases, the unhappy group will be able to “fix” it by `dnf swap`, either by `dnf swap --allowerasing nodejs-bin nodejs22-bin` to go back to stable nodejs v22, or by `dnf swap --allowerasing nodejs22-bin nodejs-bin` to keep getting updates on system upgrade. So WDYT? Which approach seems to be the better/less bad one? -- Jan Stanek Senior Software Engineer Red Hat IM: @jstanek -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
