kapouer at melix.org
Tue May 1 23:34:47 UTC 2012
On 02/05/2012 00:16, Patrick Ouellette wrote:
> On Tue, May 01, 2012 at 04:53:05PM -0500, Jonathan Nieder wrote:
>> Date: Tue, 1 May 2012 16:53:05 -0500
>> From: Jonathan Nieder <jrnieder at gmail.com>
>> Subject: Re: Node.js and it's future in debian
>> To: Patrick Ouellette <ne4po at arrl.net>
>> Cc: node at packages.debian.org, nodejs at packages.debian.org
>> (shrinking cc list because I think I've said too much on -devel already)
>> Hi Pat,
>> Patrick Ouellette wrote:
>>> I was under the impression that neither package was going to move forward with
>>> a binary named "node"
>>> The proposal was made for a transition plan to be made then the nodejs
>>> person quit talking/posting.
>> I think you misunderstood before. Ian suggested a way to move forward
>> without having to rely on good faith on both sides:
>> 1. "node" maintainer and "nodejs" maintainers prepare packages that
>> remove the "node" command.
>> 2. Maintainer of one of the two packages uploads both.
>> 3. Usual mechanisms (release team, etc) ensure that the "node"
>> command is not reintroduced.
>> I think the maintainers of both packages were ok with that, but then
>> step (1) never happened. I proposed a patch for the node package that
>> does not involve removing the "node" command, and got no response,
>> except a comment criticizing me for not being a ham radio user or
>> testing it. I proposed a patch for the nodejs package that does not
>> involve removing the "node" command, and it was applied.
> This is what I understood, and as a maintainer for "one of the packages"
> I was waiting for information from the node.js camp (agreement, etc.).
> I think the issue here is getting the nodejs maintainers onboard.
> That would be Jérémy Lal & Jonas Smedegaard. I don't recall seeing
> either of them weigh in on the issue *ever*a (I could be wrong, it is
> late in the afternoon after a long day at work.)
The issue was described by me and others in :
and summed up in this thread and the previous ones.
>From the nodejs side, i don't see what we can say that hasn't been said.
>From the hamradio side, we are just waiting for an experienced user to
explain how /usr/sbin/node is called, from command-line, from init scripts,
from shebangs ?
Are there any cheap radio hardware i could buy to test it in a real setup ?