Re: The "node" command in Debian

["Bernhard R. Link" <brlink@debian.org>]

* Jérémy Lal <jerry@edagames.com> [110207 18:21]:
> > 2. they can be forced (by the TC) to drop their claim of "node" in the
> >    common namespace.  This is not likely to happen.

If both camps can rightly argue that some other command called
"node" might make things in their camp call the wrong thing, then this
is the only reasonable solution.

> Another proposal :
>
> 5. nodejs package provides /usr/bin/nodejs, following policy.
>    nodejs-notrenamed package links /usr/bin/node to nodejs, and conflicts
>    with node package.
>
> + Both packages node and nodejs can be installed, with full functionnality.
> + If the renaming is too much a burden for the user, he can install the
>   not renamed version, knowing he can't install node package in that case.
> - Depending on nodejs-notrenamed must be impossible (is this possible ?)
> - All packages depending on nodejs must be able to work with /usr/bin/nodejs.
> - It is still violating policy, though in a more flexible and twisted way.

A user wanting to have a node command can also just create a symlink
manually (if things call only node without path, they can even just add
that into /usr/local/[s]bin without thinking about diversions (though
diversions would not really be necessary as path is essentially dead for
packages).

There is not really a need for a package if nothing can depend on it,
all tests should be done without and a user can get the same effect with
a single simple command.

	Bernhard R. Link