From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Begin a dev-libs/nodejs category?
Date: Wed, 21 Mar 2018 14:27:11 +1300 [thread overview]
Message-ID: <20180321142552.603c178b@katipo2.lan> (raw)
In-Reply-To: <534f8dd2-2174-0ca4-1493-c55c35bfa4c8@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On Tue, 20 Mar 2018 14:48:29 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:
> There's a real technical problem hidden in there. Since npm
> (recursively!) bundles every dependency, nobody worries about
> compatibility in their JS packages. You'll quickly find yourself stuck.
Honestly, I expected at some point we'd reach for slotting and normalization,
and recursive trees of symlinks....
eg:
/usr/lib/nodejs/<packagename>/<version>/lib/<dependency-name> -> /usr/lib/nodejs/<packagename>/<version>
Or something like that.
So you'd wind up with
/usr/lib/nodejs/foo/1.0/lib/bar -> /usr/lib/nodejs/bar/1.0
/usr/lib/nodejs/foo/1.0/lib/baz -> /usr/lib/nodejs/baz/2.0
/usr/lib/nodejs/bar/1.0/lib/baz -> /usr/lib/nodejs/baz/1.0
/usr/lib/nodejs/baz/1.0/...
/usr/lib/nodejs/baz/2.0/...
Or something like that. But I imagine constructing such a thing a
rather painful exercise.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-21 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:50 [gentoo-dev] [RFC] Begin a dev-libs/nodejs category? Herb Miller Jr.
2018-03-20 18:34 ` Michał Górny
2018-03-20 19:43 ` Herb Miller Jr.
2018-03-20 18:48 ` Michael Orlitzky
2018-03-20 20:14 ` Herb Miller Jr.
2018-03-20 20:44 ` Michael Orlitzky
2018-03-21 1:27 ` Kent Fredric [this message]
2018-03-21 1:36 ` M. J. Everitt
2018-03-20 23:50 ` Benda Xu
2018-03-21 1:44 ` Herb Miller Jr.
2018-03-21 7:33 ` Kent Fredric
2018-03-21 12:22 ` Herb Miller Jr.
2018-03-21 10:07 ` X dej
2018-03-21 12:15 ` [gentoo-dev] Pypi generator (Was: [RFC] Begin a dev-libs/nodejs category?) Benda Xu
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=20180321142552.603c178b@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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