Re: [Pkg-javascript-devel] /usr/bin/nodejs vs /usr/bin/node

2016-10-21 Thread Jonas Smedegaard 
Hi Daniel,

Quoting Jérémy Lal (2016-10-21 09:05:04)
> 2016-10-21 7:24 GMT+02:00 Paul Gevers :
> > On 21-10-16 06:55, Daniel Lo Nigro wrote:
> > > Given the amount of complexity stemming from Debian renaming this 
> > > binary and the fact that it breaks parts of the Node.js ecosystem, 
> > > is there any chance it will be renamed back to "node" in the 
> > > future, or for /usr/bin/node to be symlinked to /usr/bin/node 
> > > (perhaps using the update-alternatives system to allow the user to 
> > > choose whether they want to symlink nodejs or ax25-node, in case 
> > > they have both installed)?
> >
> > In Debian, we have the package nodejs-legacy which provides the 
> > symlink you request. Please read the description. Apart from text 
> > describing fact that no official Debian package may depend on it, it 
> > also contains a link to the technical committee ruling on how this 
> > came about. As the ax25-node package still exist, I see no chance at 
> > all that the current situation will change.
> >
> > As ax25-node and nodejs don't provide the same functionality, using 
> > the update-alternaives system is not appropriate.

> if you're distributing yarn in the main debian archive, i believe the 
> right way to work around this is to "Suggest" nodejs-legacy in 
> debian/control.

I disagree that above is the "right way" - here are the options you have 
as I see them:

 a) Continue to also support "nodejs" runtime
* You may suggest (but not recommend or depend on) nodejs-legacy.
* Must be usable (at least for a subset of cases) with "nodejs".

 b) Support only "node" runtime
* You should depend on or recommend nodejs-legacy
* Cannot be part of official Debian (but can be in contrib)

 c) Change ruling through the tech-ctte or a general solution vote
* Will be a tiresome and long process
* Will only become effective for next-next stable (i.e. in ~2019)
* May further tear apart our communities rather than unite

As I see it, the "right way from the POV of Debian is a), while from the 
POV of the Node.js community it is c).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] /usr/bin/nodejs vs /usr/bin/node

2016-10-21 Thread Jérémy Lal 
2016-10-21 7:24 GMT+02:00 Paul Gevers :

> Hi Daniel,
>
> On 21-10-16 06:55, Daniel Lo Nigro wrote:
> > Given the amount of complexity stemming from Debian renaming this binary
> > and the fact that it breaks parts of the Node.js ecosystem, is there any
> > chance it will be renamed back to "node" in the future, or for
> > /usr/bin/node to be symlinked to /usr/bin/node (perhaps using the
> > update-alternatives system to allow the user to choose whether they want
> > to symlink nodejs or ax25-node, in case they have both installed)?
>
> In Debian, we have the package nodejs-legacy which provides the symlink
> you request. Please read the description. Apart from text describing
> fact that no official Debian package may depend on it, it also contains
> a link to the technical committee ruling on how this came about. As the
> ax25-node package still exist, I see no chance at all that the current
> situation will change.
>
> As ax25-node and nodejs don't provide the same functionality, using the
> update-alternaives system is not appropriate.
>
>
Hello,

if you're distributing yarn in the main debian archive, i believe the right
way to
work around this is to "Suggest" nodejs-legacy in debian/control.
We're probably going to do the same with npm (but i clearly lack the time to
take care of npm).

if you're distributing it outside of debian archives, then "Recommend" is
good too.
Avoid "Depend", because it would risk breaking for users installing "nodejs"
debian package from upstream.

Note that the original package name conflict disappeared: there is no longer
a "node" binary distributed by ax25-node at all, but the "too generic a
name"
issue remains.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] /usr/bin/nodejs vs /usr/bin/node

2016-10-20 Thread Paul Gevers 
Hi Daniel,

On 21-10-16 06:55, Daniel Lo Nigro wrote:
> Given the amount of complexity stemming from Debian renaming this binary
> and the fact that it breaks parts of the Node.js ecosystem, is there any
> chance it will be renamed back to "node" in the future, or for
> /usr/bin/node to be symlinked to /usr/bin/node (perhaps using the
> update-alternatives system to allow the user to choose whether they want
> to symlink nodejs or ax25-node, in case they have both installed)?

In Debian, we have the package nodejs-legacy which provides the symlink
you request. Please read the description. Apart from text describing
fact that no official Debian package may depend on it, it also contains
a link to the technical committee ruling on how this came about. As the
ax25-node package still exist, I see no chance at all that the current
situation will change.

As ax25-node and nodejs don't provide the same functionality, using the
update-alternaives system is not appropriate.

Paul



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] /usr/bin/nodejs vs /usr/bin/node

2016-10-20 Thread Daniel Lo Nigro 
Hello Debian JavaScript maintainers!

I'm one of the developers on Yarn (https://yarnpkg.com/), a new package
manager for JavaScript designed to replace the "npm" client. As part of our
launch, I created Debian packages and am hosting them in our own repository.

For the initial release, I used #!/usr/bin/nodejs as the shebang, due to
the fact that the Debian Node.js release calls its binary "nodejs" instead
of "node". However, this caused issues on systems where people have
installed Node.js through other installation methods. In an ideal world,
all dependencies would be installed through dpkg/apt-get, but unfortunately
that's not the case in the Node.js ecosystem. Some people install Node.js
through an application called "nvm" (https://github.com/creationix/nvm),
which is designed to allow the user to toggle between different Node.js
versions. This is useful for developers to easily test their code on
multiple different Node.js versions, as using the Debian Node.js package
does not allow multiple versions to be installed concurrently.

Since nvm uses the upstream Node.js releases directly, its binaries are
named "node" instead of "nodejs". This means that I needed to modify Yarn
to use a shell script that checks for both "node" (for users of nvm and
Node.js on non-Debian platforms) and "nodejs" (for users of the Debian
node.js packages). This works for Yarn itself, but there's many many
scripts and packages on npm that rely on the binary being called "node"
rather than "nodejs" and totally fall apart on Debian/Ubuntu. A lot of
users end up symlinking /usr/local/bin/node to /usr/bin/nodejs to get a
usable environment.

Given the amount of complexity stemming from Debian renaming this binary
and the fact that it breaks parts of the Node.js ecosystem, is there any
chance it will be renamed back to "node" in the future, or for
/usr/bin/node to be symlinked to /usr/bin/node (perhaps using the
update-alternatives system to allow the user to choose whether they want to
symlink nodejs or ax25-node, in case they have both installed)?


Thank you!

Kind Regards,
Daniel
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel