All of lore.kernel.org
 help / color / mirror / Atom feed
From: "iwanicki92" <iwanicki92@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sbom30.py/spdx30_tasks.py: fix SPDX_* prefix lookup
Date: Mon, 24 Aug 2026 13:29:50 -0700	[thread overview]
Message-ID: <2283556.1787603390860269556@lists.openembedded.org> (raw)
In-Reply-To: <DKWYM6BJ4WFN.3HWMLSORAJFPP@bootlin.com>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

Posted v2 patch, issue was that I changed it to be more consistent with documentation e.g. for SPDX_IMAGE_SUPPLIER ( https://docs.yoctoproject.org/ref-manual/variables.html#term-SPDX_IMAGE_SUPPLIER ) :

> 
> If not set, no supplier information is added to the image SBOM
> 

but maybe it meant that if `<PREFIX>_*` is not set (e.g. _name or _type), then this information is not added.
So with this change it'll be possible to use `SPDX_IMAGE_SUPPLIER = "MY_COMPANY"` or undocumented `SPDX_IMAGE_SUPPLIER_ref = "MY_COMPANY"` (which doesn't pass all arguments it was called with (e.g. `add`), so it feels like a bug but I don't know enough about this subsystem to tell) with variable with no suffix having priority.

Another way to fix it would be to maybe change documentation and say explicitly to use SPDX_IMAGE_SUPPLIER_ref and that SPDX_IMAGE_SUPPLIER without any suffix is not used.

[-- Attachment #2: Type: text/html, Size: 1065 bytes --]

      reply	other threads:[~2026-08-24 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 21:17 [PATCH] sbom30.py/spdx30_tasks.py: fix SPDX_* prefix lookup iwanicki92
2026-08-24  6:28 ` [OE-core] " Mathieu Dubois-Briand
2026-08-24 20:29   ` iwanicki92 [this message]

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=2283556.1787603390860269556@lists.openembedded.org \
    --to=iwanicki92@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.