Re: Node.js and it's future in debian
I think using the alternatives system  could be a solution. I guess
that node.js and axnode is not often used on the same system. Therefore
in most of the cases the alternatives auto select mechanism will do the
In the case that both programs are installed, the node symlink is auto
selected by the priority so I would suggest to set the priority of
axnode higher because it was first there.
Anyone who want to have node.js as node can simply set the alternatives
to manual selection.
This approach can be combined with the long term goal to have no node
binary. You make node a shell script which prints a warning and then
calls the binary selected by the alternatives system.
Am Thu, 03 May 2012 13:05:21 -0400
schrieb Patrick Ouellette <firstname.lastname@example.org>:
> Thanks for the comments!
> On Thu, May 03, 2012 at 08:33:43AM -0700, David Ranch wrote:
> > From my experience, many MANY Linux hams have customized scripts
> > that startup some very elaborate HAM systems. For many, these
> > scripts weren't written by them and the changing of the node command
> > could be very difficult for some. The other aspect is if this
> > change came into a package update that could impact production
> > systems in VERY remote sites. This could cause all kinds ugliness
> > that can be easily avoided.
> One issue here seems to be a perception problem. The non-ham folks
> look at the ax25 how to or similar documentation and see that node is
> "usually called from ax25d" or a similar superserver. This leads them
> to believe that the command is only started from one or two "easily
> identified and modified" scripts.
> The Node.js side argues that there are many books, tutorials, and
> scripts that tell the user to run "node <script>" and so the
> interaction of the user and node.js' node command is direct and
> > I can appreciate Debian's goal to keep things moving forward but I'd
> > argue that a binary name of "/usr/sbin/nodejs" would be a lot more
> > informative with the two additional characters than just calling it
> > "node" (and disrupting a well known binary name for us Linux packet
> > hams).
> I completely agree, but apparently Node.js' upstream has changed the
> name once previously (apparently from a similar problem) and while
> acknowledging the name is generic and a poor choice refuses to
> consider another change. (According to what I can tell from the
> Debian discussion. I have not talked to Node.js upstream personally.)
> FWIW, the commands are NOT in the same path. The ham radio node
> command is /usr/sbin/node and the Node.js command is /usr/bin/node
> Debian does NOT allow binaries with the same name to have different
> functions. Unfortunately "first come, first served" is not the policy
> To unsubscribe from this list: send the line "unsubscribe linux-hams"
> in the body of a message to email@example.com
> More majordomo info at http://vger.kernel.org/majordomo-info.html