Am 24.10.19 um 14:12 schrieb Alexander Kanavin:
On Thu, 24 Oct 2019 at 14:02, Stefan Herbrechtsmeier
<[email protected] <mailto:[email protected]>> 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.
Do you have an example package?
I very much welcome a solution that uses 'npm install' in a way that
preserves offline builds, and integrity/reproducibility of downloads.
Fist we should use 'npm ci' instead of 'npm install'.
How would you handle prebuild binaries? Would you disable prebuild binaries?
How would you handle native packages (ex. angular-cli)?
How would you patch dependencies?
How would you remove unneeded files (ex. documentation, examples, source
code)?
License management should be also handled by npm, and if it isn't, then
we need to work with the upstream to address it.
To my knowledge npm don't check license files. It only reads the license
in the package.json.
Regards
Stefan
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
