Should not at least @debian.org addresses by default be whitelisted on
the tech-ctte list?
Date: Thu, 3 May 2012 22:33:51 +0000 (UTC)
Subject: Re: Re: Bug#614907: nodejs/node command conflict: why can't we have
You are not subscribed to this list, so your submission was rejected.
Please subscribe to the list first and then repost your message.
A copy of your submission is included below.
* Jonathan Nieder [2012-05-02 18:56 -0500]:
Jonathan Nieder wrote:
> I'd be happy to talk about work so far, transition plans,
> complications and possible ways forward in a separate message.
This seems like a long shot, but the maintainers of both packages
seemed to like it, so let's give mentioning it a try:
Assuming we go through with the transition, no package in Debian would
use the "node" command. At this point, as far as transition plans go,
it doesn't matter what the "node" command does it could have some
other effect entirely.
Now what if we provide both /usr/bin/node and /usr/sbin/node?
Bash uses /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
as path if $PATH is not set, so /usr/sbin before /usr/bin in the path is
not that unlikely.
A user installs node to get node.js and notices that it is the wrong
program, then he installs the correct package nodejs and notices that
the command node still does not what's expected. Does not sound like
a solution to me.
As Marco mentioned on debian-devel, there is nothing but our
stubbornness and good sense stopping us from doing that.
"I want to do packet radio and to programm in node.js on my computer,
why is this not possible with Debian."
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org