From: Jonathan Nieder <jrnieder@gmail.com>
To: Patrick Ouellette <pouelle@debian.org>
Cc: David Ranch <linux-hams@trinnet.net>,
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, 3 May 2012 13:51:29 -0500 [thread overview]
Message-ID: <20120503185129.GA18768@burratino> (raw)
In-Reply-To: <20120503170521.GD19468@flying-gecko.net>
Hi again,
Patrick Ouellette wrote:
> I completely agree, but apparently Node.js' upstream has changed the name
> once previously (apparently from a similar problem) and while acknowledging
> the name is generic and a poor choice refuses to consider another change.
> (According to what I can tell from the Debian discussion. I have not
> talked to Node.js upstream personally.)
The working title of Node.js was "server" for a few weeks, before
anyone was using it. When I looked that up in order to understand
what the name "node" was about (in the spirit of [1]) I mentioned this
factoid without making the context sufficiently clear, and I'm sorry
about that[2].
To avoid banging heads against the wall too quickly: I think there are
two aspects that it would be productive to discuss:
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.)
2. What should be the state in Debian's upcoming "wheezy" release to
provide a smooth upgrade path and not surprise users too much?
(My answer is that configuration needs to be smoothly migrated:
- ax25d.conf by the ax25-tools package
- inetd configuration by the node package
- other configuration by the sysadmin, after they are notified
through a note in node's NEWS.Debian file (shown by
apt-listchanges) and the release notes
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 you disagree with the long-term goal or have ideas for a smoother
migration, that could be useful.
Hope that helps,
Jonathan
[1] http://wiki.debian.org/WhyTheName
[2] https://lists.debian.org/debian-devel/2011/11/msg00377.html
next prev parent reply other threads:[~2012-05-03 18:51 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 [this message]
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
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=20120503185129.GA18768@burratino \
--to=jrnieder@gmail.com \
--cc=debian-hams@lists.debian.org \
--cc=linux-hams@trinnet.net \
--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.