Margarita Manterola <marga@debian.org> writes: > Hi, > > Unfortunately the initial reassign message didn't make it to the debian-ctte > list, so quoting it here for context: > >> Control: retitle -1 Rename nodejs back to node for buster, now that >> ax25-node has been removed? > >> Dear tech-ctte, >> >> In 2012, the decision was made to rename Node.js' "node" name to >> nodejs-legacy, and transition the existing "node" package to ax25-node. >> However, ax25-node (and the "node" package following) were removed in >> 2015 citing lack of activity: >> https://packages.qa.debian.org/n/node.html >> >> Thus, would it be possible to revert the original decision, and rename >> nodejs back to node in the next Debian release? Doing so would make >> working with JavaScript programs outside of Debian a lot easier, as >> projects tend to hardcode the "node" interpreter name. > > I have just re-read parts of the discussion from 2012 (it was a very long and > heated discussion that spanned multiple bugs and mailing lists). > > Part of the reasoning that was taken into account when deciding that neither the > old node nor the new node would keep the node command line was that "node" is > too common of a name to be a good command line name. > > This is still true today. However, 5 years after the initial decision, the use > of Node.js has kept growing to the point that it is by far the most expected > meaning of the word "node" in the IT context. > > This, compounded with the fact that the old node will be gone in stretch, means > that it makes sense for nodejs to become node. > > Does anyone think differently? Assuming that we're only talking about the name of the binary that the nodejs package installs (rather than renaming the package itself), then I think it is reasonable for nodejs-legacy to effectively be merged into the nodejs package. I presume we'd want to continue providing /usr/bin/nodejs for people that have switched to using that, so that might as well continue to be the name of the binary, since that gives us a 'node' symlink that is self-documenting. If ax25-node reenters the archive at some point, that should now be no problem, since AIUI it now provides only an ax25-node binary (which is not directly run by users). Is there any need to have a versioned Conflicts against old versions of ax25-node/node? Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
Attachment:
signature.asc
Description: PGP signature