From: Adrian Bunk <bunk@stusta.de>
To: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Cc: "Paul Eggleton \(paul.eggleton@linux.intel.com\)"
<paul.eggleton@linux.intel.com>,
rennes@savoirfairelinux.com,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 0/6] NPM refactoring
Date: Fri, 25 Oct 2019 14:08:49 +0300 [thread overview]
Message-ID: <20191025110849.GB17425@localhost> (raw)
In-Reply-To: <a83142c2-9106-f996-d1d9-380cbf8d2b97@herbrechtsmeier.net>
On Fri, Oct 25, 2019 at 10:35:20AM +0200, Stefan Herbrechtsmeier wrote:
> Am 24.10.19 um 17:59 schrieb Richard Purdie:
> > On Thu, 2019-10-24 at 18:37 +0300, Adrian Bunk wrote:
> > > On Thu, Oct 24, 2019 at 02:12:43PM +0200, Alexander Kanavin wrote:
> > > > On Thu, 24 Oct 2019 at 14:02, Stefan Herbrechtsmeier <
> > > > stefan@herbrechtsmeier.net> wrote:
> > > >
> > > > > @Richard: What is your opinion about the per recipe dependency?
> > > > > Typically OE use one recipe per project. The NPM based solution
> > > > > handle a
> > > > > project and all dependencies via one recipe.
> > > >
> > > > I don't think it's at all realistic to stick to the 'one recipe per
> > > > component' in node.js world. A typical 'npm install' can pull down
> > > > hundreds, or over a thousand dependencies, it's not feasible to
> > > > have a
> > > > recipe for each.
> > >
> > > Debian has for the perl/python/node/go/rust/haskell ecosystems
> > > one recipe per component, with ~ 1k recipes each.
> >
> > I think we'll have to end up having a smaller number of recipes which
> > generate multiple packages. That gives a reasonable parsing time at the
> > expense of having to pre-generate some of the recipe, a bit like the
> > core perl and python recipes work today. The exact split will depend on
> > the ecosystems and the "blocks" people tend to build in as its a
> > compromise between building too much and parsing time.
>
> How should this work? Node.js consist of multiple independent packages and
> every package define its own dependencies. Thereby the dependencies is
> defined with a version range which often reference a single version.
Yes, it is a problem that backwards compatibility is frequently broken
in Node.js packages and just using npm might result in 10 different
versions of the same package installed and used.
This is a huge mess that either has to be sorted out when packaging
(as is done in Debian), or you end up with security support basically
impossible for something very exposed on the internet.
> Regards
> Stefan
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-10-25 11:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 9:03 [RFC][PATCH 0/6] NPM refactoring Jean-Marie LEMETAYER
2019-10-22 9:03 ` [RFC][PATCH 1/6] npm.bbclass: refactor the npm class Jean-Marie LEMETAYER
2019-10-22 11:35 ` Alexander Kanavin
2019-10-23 13:17 ` Jean-Marie LEMETAYER
2019-10-24 11:22 ` Stefan Herbrechtsmeier
2019-10-24 15:13 ` Jean-Marie LEMETAYER
2019-10-22 9:03 ` [RFC][PATCH 2/6] devtool: update command line options for npm Jean-Marie LEMETAYER
2019-10-22 9:03 ` [RFC][PATCH 3/6] recipetool/create_npm.py: refactor the npm recipe creation handler Jean-Marie LEMETAYER
2019-10-22 9:03 ` [RFC][PATCH 4/6] devtool/standard.py: update the append file for the npm recipes Jean-Marie LEMETAYER
2019-10-22 9:03 ` [RFC][PATCH 5/6] recipetool/create.py: replace 'latest' keyword for npm Jean-Marie LEMETAYER
2019-10-22 9:03 ` [RFC][PATCH 6/6] recipetool/create.py: remove the 'noverify' url parameter Jean-Marie LEMETAYER
2019-10-22 11:22 ` [RFC][PATCH 0/6] NPM refactoring Richard Purdie
2019-10-23 13:17 ` Jean-Marie LEMETAYER
2019-10-24 12:01 ` Stefan Herbrechtsmeier
2019-10-24 12:12 ` Alexander Kanavin
2019-10-24 12:40 ` Stefan Herbrechtsmeier
2019-10-24 12:45 ` Alexander Kanavin
2019-10-24 13:52 ` Stefan Herbrechtsmeier
2019-10-24 14:22 ` Alexander Kanavin
2019-10-24 17:44 ` Stefan Herbrechtsmeier
2019-10-24 17:58 ` Alexander Kanavin
2019-10-25 8:58 ` Stefan Herbrechtsmeier
2019-10-24 15:13 ` Jean-Marie LEMETAYER
2019-10-24 17:03 ` Stefan Herbrechtsmeier
2019-10-24 13:36 ` richard.purdie
2019-10-24 15:20 ` Jean-Marie LEMETAYER
2019-10-24 15:37 ` Adrian Bunk
2019-10-24 15:59 ` Richard Purdie
2019-10-25 8:35 ` Stefan Herbrechtsmeier
2019-10-25 11:08 ` Adrian Bunk [this message]
2019-10-27 9:58 ` Stefan Herbrechtsmeier
2019-10-24 15:13 ` Jean-Marie LEMETAYER
2019-10-24 16:18 ` Stefan Herbrechtsmeier
2019-10-25 8:01 ` André Draszik
2019-10-25 9:10 ` Stefan Herbrechtsmeier
2019-10-29 10:52 ` André Draszik
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=20191025110849.GB17425@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=rennes@savoirfairelinux.com \
--cc=stefan@herbrechtsmeier.net \
/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.