Re: Bug#597571: nodejs: non common executable name (exclusive alternatives ?)

2010-09-22 Thread Neil Williams
On Thu, 23 Sep 2010 01:32:21 +0200 Jérémy Lal wrote: > On 23/09/2010 01:24, Ian Jackson wrote: > > Jérémy Lal writes ("Re: Bug#597571: nodejs: non common executable > > name (exclusive alternatives ?)"): > >> On might object "node" would have a diffe

Re: Bug#597571: nodejs: non common executable name (exclusive alternatives ?)

2010-09-22 Thread Jérémy Lal
On 23/09/2010 01:24, Ian Jackson wrote: > Jérémy Lal writes ("Re: Bug#597571: nodejs: non common executable name > (exclusive alternatives ?)"): >> On might object "node" would have a different meaning, depending >> on the packages installed ; still, nodejs

Re: Bug#597571: nodejs: non common executable name (exclusive alternatives ?)

2010-09-22 Thread Ian Jackson
Jérémy Lal writes ("Re: Bug#597571: nodejs: non common executable name (exclusive alternatives ?)"): > On might object "node" would have a different meaning, depending > on the packages installed ; still, nodejs or x25node (if its maintainer > cares to follow) would

Re: Bug#597571: nodejs: non common executable name (exclusive alternatives ?)

2010-09-22 Thread Jérémy Lal
On 21/09/2010 18:01, Patrick Ouellette wrote: > On Tue, Sep 21, 2010 at 05:26:30PM +0200, Mehdi Dogguy wrote: >> >> Did you say that before? I don't think so. Personally, I care about the >> Debian package only because the original bugreport (from where this >> discussion started) was against the D

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Patrick Ouellette
On Tue, Sep 21, 2010 at 05:26:30PM +0200, Mehdi Dogguy wrote: > > Did you say that before? I don't think so. Personally, I care about the > Debian package only because the original bugreport (from where this > discussion started) was against the Debian package and for a Debian > specificity, not a

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Patrick Ouellette
On Tue, Sep 21, 2010 at 05:07:39PM +0200, Mehdi Dogguy wrote: > > On 21/09/2010 16:02, Patrick Ouellette wrote: > > On Tue, Sep 21, 2010 at 03:54:41PM +0200, Mehdi Dogguy wrote: > >> > >> Wrong. nodejs still provides the binary nodejs and not _node_. So, > >> nodejs can stay as is. The rename wo

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Mehdi Dogguy
On 21/09/2010 17:22, Patrick Ouellette wrote: > > You are quick with the "wrong" button. It's my new toy :) > The UPSTREAM nodejs is /usr/bin/node. The Debian package renamed it to > nodejs. > Did you say that before? I don't think so. Personally, I care about the Debian package only because

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Patrick Ouellette
On Tue, Sep 21, 2010 at 03:54:41PM +0200, Mehdi Dogguy wrote: > > Wrong. nodejs still provides the binary nodejs and not _node_. So, nodejs can > stay as is. The rename would be necessary if both packages provide the > same binary (same filename), which is not the case here. > Actually, from the

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Mehdi Dogguy
On 21/09/2010 16:02, Patrick Ouellette wrote: > On Tue, Sep 21, 2010 at 03:54:41PM +0200, Mehdi Dogguy wrote: >> >> Wrong. nodejs still provides the binary nodejs and not _node_. So, >> nodejs can stay as is. The rename would be necessary if both >> packages provide the same binary (same filename

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Jérémy Lal
Note that i tried to warn upstream nodejs several months ago, but it was already too late, so i renamed it to comply. Please also note that nodejs runs (js) scripts, so the renaming means each nodejs module[0] that may be packaged in the future, and that provides executables, will need to be patch

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Ian Jackson
Mehdi Dogguy writes ("Re: Bug#597571: nodejs: non common executable name"): > Wrong. nodejs still provides the binary nodejs and not _node_. So, nodejs can > stay as is. The rename would be necessary if both packages provide the > same binary (same filename), which is not th

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Mehdi Dogguy
On 21/09/2010 14:48, Ian Jackson wrote: > Carl Fürstenberg writes ("Re: Bug#597571: nodejs: non common executable > name"): >> Policy only states "The maintainers should report this to the >> debian-devel mailing list and try to find a consensus about which >&

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Patrick Ouellette
On Tue, Sep 21, 2010 at 01:48:03PM +0100, Ian Jackson wrote: > > Carl Fürstenberg writes ("Re: Bug#597571: nodejs: non common executable > name"): > > Policy only states "The maintainers should report this to the > > debian-devel mailing list and try to find

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Ian Jackson
Carl Fürstenberg writes ("Re: Bug#597571: nodejs: non common executable name"): > Policy only states "The maintainers should report this to the > debian-devel mailing list and try to find a consensus about which > program will have to be renamed. If a consensus cannot be

Re: Bug#597571: nodejs: non common executable name

2010-09-21 Thread Jérémy Lal
On 21/09/2010 02:00, Carl Fürstenberg wrote: > 2010/9/21 Jérémy Lal : I also contacted debian-hams to see if they'd mind changing this binary name, and the answer is clearly no [1]. [1] http://lists.debian.org/debian-hams/2010/08/msg00031.html i posted a reply yesterday

Re: Bug#597571: nodejs: non common executable name

2010-09-20 Thread Carl Fürstenberg
2010/9/21 Jérémy Lal : > On 21/09/2010 01:31, Carl Fürstenberg wrote: >> On Tue, Sep 21, 2010 at 00:46, Jérémy Lal wrote: >>> On 21/09/2010 00:27, Carl Fürstenberg wrote: Package: nodejs Version: 0.2.2-1 Severity: normal in debian, the executable name is set to "nodejs"; t