[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-javascript-devel] Node.js and it's future in debian

OoO Pendant le journal télévisé du lundi 07 mai 2012, vers 20:41, Philip
Hands <phil@hands.com> disait :

>> Package: node
>> Depends: ax25-node
>> Conflicts: nodejs
>> -- /usr/sbin/node -> /usr/sbin/ax25-node
>> Package: ax25-node
>> -- /usr/sbin/ax25-node
>> Package: nodejs
>> Conflicts: node
>> -- /usr/bin/nodejs
>> -- /usr/bin/node -> /usr/bin/nodejs
>> > So this would need package replacement, which is a pain, and an
>> > exception for a policy violation -- is that enough to kill the idea?
>> I think it's an acceptable compromise under the circumstances.

> This seems a little one-sided, as it inflicts the bulk of the work on
> those that are less to blame.

I  don't  see  the  point   to  perfect  symmetry:  nodejs  contains  an
interpreter while ax25-node  contains a daemon and will  work out of the
box for most people (those that don't need custom scripts).

My point is that nodejs without /usr/bin/node is useless.

> It also prevents a HAM from deciding to dabble in Node.js while
> preserving the 'node' name for their ax25 use.

For this point only:

Package: nodejs
Depends: nodejs-interpreter
Conflicts: node
-- /usr/bin/node -> /usr/bin/nodejs

Package: nodejs-interpreter
-- /usr/bin/nodejs

But one additional package for people we are not even sure they exist...

> I don't really see the point of adding the symlink to nodejs if you're
> not putting it in a separate package -- one of the reasons I had for
> doing that split was that it might allow us to later provide popcon
> stats of the proportion's of node.js users that install the symlink
> package as part of evidence to persuade upstream that it might be worth
> entertaining a better binary name -- having them both in the same
> package discards that information.

I doubt that upstream will  rename anything after years of use. Upstream
also has a community to please.  And popcon may just be an indication on
the number  of our users that  are pissed enough to  install from source
because installing "nodejs" package did not deliver the right command.
Vincent Bernat ☯ http://vincent.bernat.im

printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?\n");
	2.2.16 /usr/src/linux/drivers/char/msp3400.c

Attachment: pgpFGTCHCLWEV.pgp
Description: PGP signature

Reply to: