From: "iwanicki92" <iwanicki92@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] sbom30.py/spdx30_tasks.py: fix SPDX_* prefix lookup
Date: Mon, 24 Aug 2026 22:48:45 -0700 [thread overview]
Message-ID: <2283556.1787636925763155083@lists.openembedded.org> (raw)
In-Reply-To: <CAJdd5GZsDEKtHL3pNjuqg6xEOWLFMDbGUibbobjus3XJR-8BLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
>
> I'm not sure where the documentation you found suggests this
>
The Yocto Project documentation: https://docs.yoctoproject.org/ref-manual/variables.html#term-SPDX_IMAGE_SUPPLIER contains almost the same example:
MY_COMPANY_name = "Acme Corp"
MY_COMPANY_type = "organization"
SPDX_IMAGE_SUPPLIER = "MY_COMPANY"
SPDX_SDK_SUPPLIER = "MY_COMPANY"
the support for this is already implemented by undocumented `_ref` suffix, so maybe documentation should be changed instead.
Though `_ref` suffix if I'm reading code correctly allows for infinite chaining e.g:
SPDX_IMAGE_SUPPLIER_ref = "MY_COMPANY1"
MY_COMPANY1_ref = "MY_COMPANY2"
MY_COMPANY2_name = "Acme Corp
>
> but the values for any base variable are suffixes always appended to that
> base variable
>
>
> SPDX_IMAGE_SUPPLIER = "MY_COMPANY"
> SPDX_IMAGE_SUPPLIER_MY_COMPANY_name = "CCCC"
> SPDX_IMAGE_SUPPLIER_MY_COMPANY_type = "organization"
>
This one I don't think is mentioned anywhere, and also doesn't work. Maybe you meant SPDX_AUTHORS which has this syntax:
SPDX_AUTHORS ??= "openembedded"
SPDX_AUTHORS[doc] = "A space separated list of the document authors. Each item \
is used to name a base variable like SPDX_AUTHORS_<AUTHOR> that \
describes the author."
SPDX_AUTHORS_openembedded_name = "OpenEmbedded"
SPDX_AUTHORS_openembedded_type = "organization"
[-- Attachment #2: Type: text/html, Size: 1716 bytes --]
next prev parent reply other threads:[~2026-08-25 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 20:10 [PATCH v2] sbom30.py/spdx30_tasks.py: fix SPDX_* prefix lookup iwanicki92
2026-08-24 23:26 ` [OE-core] " Joshua Watt
2026-08-25 5:48 ` iwanicki92 [this message]
2026-08-25 15:00 ` Joshua Watt
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.1787636925763155083@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.