* NPM recipe license upgrade
@ 2026-07-30 17:04 John Ripple
0 siblings, 0 replies; only message in thread
From: John Ripple @ 2026-07-30 17:04 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Hi,
I have a recipe that builds an npm project using the git and npmsw fetchers. The git fetcher pulls the project's source code and the npmsw fetcher is used to get all the npm dependencies.
>
> SRC_URI = "git://... \
> npmsw://... "
>
Whenever I change the npm project in the git repo and update the npm-shrinkwrap.json file I then need to update all the licenses for the individual components in the shrinkwrap file. I've tried using devtool add/upgrade but neither option seems to cover the case with a git repo being the source of an npm project.
I also noticed when I did use the npm and npmsw fetchers on another recipe with devtool add it often misidentified the dependencies' license types. For example, I was seeing most npm dependencies with MIT licenses were misidentified as X11 licenses. Since the license types for every npm dependency are listed in the npm-shrinkwrap.json file, is there any way to use the npm-shrinkwrap.json file with devtool when updating licenses?
What is the preferred way to automate updating licenses of these types of recipes?
It's also worth noting I have been using Thomas Perrot's patches in the bitbake mailing list for the npm fetcher on Wrynose. https://lists.openembedded.org/g/bitbake-devel/topic/119833197#msg19846
Thanks,
John
[-- Attachment #2: Type: text/html, Size: 1668 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-07-30 17:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-30 17:04 NPM recipe license upgrade John Ripple
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox