openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: "John Ripple" <john.ripple@keysight.com>
To: openembedded-core@lists.openembedded.org
Subject: NPM recipe license upgrade
Date: Thu, 30 Jul 2026 10:04:02 -0700	[thread overview]
Message-ID: <FtYb.1785431042033346907.8M2E@lists.openembedded.org> (raw)

[-- 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 --]

                 reply	other threads:[~2026-07-30 17:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=FtYb.1785431042033346907.8M2E@lists.openembedded.org \
    --to=john.ripple@keysight.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).