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 <
ste...@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.
Regards
Stefan
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
