From: Stefano Tondo <stondo@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: stefano.tondo.ext@siemens.com, adrian.freihofer@siemens.com,
Peter.Marko@siemens.com, jpewhacker@gmail.com,
Ross.Burton@arm.com
Subject: [PATCH 0/2] spdx-common: Documentation and extensibility improvements
Date: Sat, 21 Feb 2026 05:25:28 +0100 [thread overview]
Message-ID: <20260221042530.318125-1-stondo@gmail.com> (raw)
From: Stefano Tondo <stefano.tondo.ext@siemens.com>
This small series improves documentation and extensibility for SPDX
configuration variables in spdx-common.bbclass.
Patch 1: Clarify SPDX_NAMESPACE_PREFIX documentation to recommend
organization-specific namespace prefixes, similar to SPDX_UUID_NAMESPACE.
Patch 2: Make SPDX_LICENSES extensible by supporting a list of license
files. This allows layers to add custom license definitions without
copying the entire oe-core license file. Also improves documentation
for when SPDX_LICENSES needs to be set (non-oe-core licenses).
Stefano Tondo (2):
spdx-common: Add documentation for undocumented SPDX variables
spdx-common: Clarify documentation and make SPDX_LICENSES extensible
meta/classes/spdx-common.bbclass | 31 +++++++++++++++++++++++++++++++
meta/lib/oe/spdx_common.py | 31 +++++++++++++++++++++++++++----
2 files changed, 58 insertions(+), 4 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-21 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 4:25 Stefano Tondo [this message]
2026-02-21 4:25 ` [PATCH 1/2] spdx-common: Add documentation for undocumented SPDX variables Stefano Tondo
2026-02-21 4:25 ` [PATCH 2/2] spdx-common: Clarify documentation and make SPDX_LICENSES extensible Stefano Tondo
2026-02-21 16:50 ` Joshua Watt
-- strict thread matches above, loose matches on Subject: below --
2026-02-21 5:16 [PATCH 0/2] spdx-common: Documentation and extensibility improvements Stefano Tondo
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=20260221042530.318125-1-stondo@gmail.com \
--to=stondo@gmail.com \
--cc=Peter.Marko@siemens.com \
--cc=Ross.Burton@arm.com \
--cc=adrian.freihofer@siemens.com \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefano.tondo.ext@siemens.com \
/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