Hi,
Am 06.10.2021 um 11:47 schrieb Alexander Kanavin:
The OE landscape is littered with unmaintained or barely maintained
layers. By the looks of things, no one wants to maintain this proposed
meta-nodejs layer either, which involves thousands of recipes, (so far)
non-existent tooling to create and update them in scalable ways, and
rigorous testing. Or such a layer would have already happened.
It's for this reason that I think the shrinkwrapped, self-contained
recipe approach is more viable (even if it comes with its own pain
points) and also matches how node.js community operates - we can fix the
CVE stuff as well to look into dependencies if that's a concern.
How should we run build scripts which need native npm packages and how
should we handle licenses of build and runtime packages?
A simplified node.js flow looks like the following
cd ${S}
rm -rf node_modules
npm install --arch=$NPM_BUILD_ARCH --dev
npm run-script --arch=$NPM_BUILD_ARCH build
rm -rf node_modules
npm install --arch=$NPM_TARGET_ARCH --global <OR> cp -r dist/* ${D}
Should we split it into two recipes or should we handle everything in a
single recipe?
Is it accepted to use the output of a native recipe as source for an
target recipe?
Regards
Stefan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157115):
https://lists.openembedded.org/g/openembedded-core/message/157115
Mute This Topic: https://lists.openembedded.org/mt/86089523/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
