All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Patrick Ouellette <pouelle@debian.org>,
	node@packages.debian.org, nodejs@packages.debian.org,
	debian-hams@lists.debian.org, linux-hams@vger.kernel.org
Subject: Re: Node.js and it's future in debian
Date: Thu, 03 May 2012 21:09:35 -0700	[thread overview]
Message-ID: <4FA3567F.2020707@trinnet.net> (raw)
In-Reply-To: <20120503185129.GA18768@burratino>


Me again..

AX.25 in Linux has been around for a long time so I can excuse it's 
overly generic "node" name purely based upon it's age but..


> The working title of Node.js was "server" for a few weeks, before
> anyone was using it.

Wow.. that's horrible!  Obviously we don't want stuff like that to 
happen.  Please also consider that all this ISN'T just a *Debian* 
problem.  Its a Linux distro-wide problem.  It's groups like this that 
form and guide aspects of all Linux distributions consistency and 
considering Debian's wide influence, changes here will surely trickle 
into other distributions over time.

It's also worth touching on that I personally appreciate the work that
Patrick Ouellette has done on maintaining the HAM packages for Debian. 
Like always, there are never enough appreciative people in this world 
but once removed / renamed /etc, I'm SURE a lot of people will come out 
of the woodwork to bitch about it.  A *lot* of people use Debian and 
Debian-related distributions with Packet radio.


>   1. Which package should use the name "node" in the long term?  What
>      can we do to ensure that happens eventually?
>
>      (My answer is that I hope that neither uses the name "node" in
>      the long term.)

I personally think that some of it SHOULD be a first come, first served 
thing.  I previously mentioned in the previous email that all of the 
various scripts that people run could/would break.  Probably no big deal 
to many of us on *this* list but trust me, I know a few Linux packet 
people who would be seriously lost because of these changes.

Also consider the tons of documentation, notably the AX.25 HOWTO that 
would be impacted and I highly doubt it would get updated (hasn't been 
since 2001) to reflect these changes.  It's not like things have needed 
to change all that much - http://tldp.org/HOWTO/AX25-HOWTO/


>   2. What should be the state in Debian's upcoming "wheezy" release to
>      provide a smooth upgrade path and not surprise users too much?

Is Node.js a new addition to Debian?  Again, I side with first come 
first served.


>      I also would hope that wheezy can include a /usr/sbin/node file
>      that prints a message to help people notice they are still using
>      it and calls /usr/sbin/axnode, but that is still under discussion.
>
>      Likewise, the Node.js needs some migration to ensure scripts
>      installed by Debian packages and from outside use the new name.
>      I would hope that wheezy can include a /usr/bin/node synonym for
>      compatibility until usage of it fades away, but that is still
>      under discussion.)

If for some reason Debian feels that longstanding packages and their 
well known binary names can be renamed at any given time (I seriously 
disagree with that mentality btw), I'd say then ALSO force the change of 
the "node" in Node.JS name to something more sane.  Don't remove one 
poorly named file for a new poorly named one just because it's new and 
shiny.

--David

  parent reply	other threads:[~2012-05-04  4:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACxjfDH5zYth6Q-ZDLDafqNEczbF3BqaGRcAhsaiPEnApbiUuA@mail.gmail.com>
     [not found] ` <20120501205524.GI30521@flying-gecko.net>
     [not found]   ` <20120501215305.GA1250@burratino>
     [not found]     ` <20120501221659.GA11430@flying-gecko.net>
     [not found]       ` <20120502065003.GB2410@burratino>
     [not found]         ` <20120502165031.GC7390@flying-gecko.net>
     [not found]           ` <20120502171349.GA23806@burratino>
2012-05-02 20:04             ` Node.js and it's future in debian Patrick Ouellette
2012-05-02 20:31               ` Jonathan Nieder
2012-05-03 15:29               ` David Ranch
2012-05-03 15:33               ` David Ranch
2012-05-03 16:17                 ` Marius Petrescu
2012-05-03 17:08                   ` Patrick Ouellette
2012-05-03 17:05                 ` Patrick Ouellette
2012-05-03 18:51                   ` Jonathan Nieder
2012-05-03 19:48                     ` Gordon JC Pearc e
2012-05-03 23:10                     ` Hans-Peter F. Oeste
2012-05-04  4:09                     ` David Ranch [this message]
2012-05-04  4:28                       ` Ray Wells
2012-05-04  4:46                       ` Jonathan Nieder
2012-05-04 12:31                   ` DL1SIG
2012-05-04 13:29                     ` [Pkg-javascript-devel] " Emilien Klein
2012-05-04 14:31                     ` Patrick Ouellette
2012-05-04  7:38               ` walter harms

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA3567F.2020707@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=debian-hams@lists.debian.org \
    --cc=jrnieder@gmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=node@packages.debian.org \
    --cc=nodejs@packages.debian.org \
    --cc=pouelle@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.