From: Patrick Ouellette <pat@flying-gecko.net>
To: DL1SIG <dl1sig@hw42.dyndns.org>
Cc: Patrick Ouellette <pouelle@debian.org>,
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: Fri, 04 May 2012 10:31:32 -0400 [thread overview]
Message-ID: <20120504143132.GA24655@flying-gecko.net> (raw)
In-Reply-To: <20120504143129.0d9a7955@hw42.dyndns.org>
On Fri, May 04, 2012 at 02:31:29PM +0200, DL1SIG wrote:
>
> I think using the alternatives system [1] could be a solution. I guess
> that node.js and axnode is not often used on the same system. Therefore
> in most of the cases the alternatives auto select mechanism will do the
> right thing.
>
While the alternatives system could be used in this manner, we are
back to a policy type issue. From the wiki:
"The Debian alternatives system creates a way for several programs
that fullfill the same or similar functions to be listed as alternative
implementations that are installed simultaneously but with one
particular implementation designated as the default."
The packages in question are worlds apart in what they do. They are not
alternatives or substitutes.
Pat
next prev parent reply other threads:[~2012-05-04 14:31 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
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 [this message]
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=20120504143132.GA24655@flying-gecko.net \
--to=pat@flying-gecko.net \
--cc=debian-hams@lists.debian.org \
--cc=dl1sig@hw42.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox