From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH v2 5/8] ref-manual/variables.rst: document the SPDX_CONCLUDED_LICENSE variable
Date: Fri, 20 Mar 2026 11:46:23 +0100 [thread overview]
Message-ID: <20260320-release-notes-6-0-v2-5-1bdb1eb142ae@bootlin.com> (raw)
In-Reply-To: <20260320-release-notes-6-0-v2-0-1bdb1eb142ae@bootlin.com>
Document the SPDX_CONCLUDED_LICENSE variable, added by commit
bb21c6a429a2 ("spdx30_tasks: Add concluded license support with
SPDX_CONCLUDED_LICENSE") in OE-Core.
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
documentation/ref-manual/variables.rst | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 6c779e42d..03154a866 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -9191,6 +9191,22 @@ system and gives an overview of their function and contents.
(+ 0.07\% with the tested image), compared to just enabling
:term:`SPDX_INCLUDE_SOURCES`.
+ :term:`SPDX_CONCLUDED_LICENSE`
+ The :term:`SPDX_CONCLUDED_LICENSE` variable allows overriding the
+ ``hasConcludedLicense`` object to individual SBOM packages. This can be
+ used when the license of a package was determined to be different than the
+ original license string value, after analysis.
+
+ This variable can be set in two ways:
+
+ - For the entire recipe::
+
+ SPDX_CONCLUDED_LICENSE = "MIT & Apache-2.0"
+
+ - For an individual package produced by the recipe::
+
+ SPDX_CONCLUDED_LICENSE:${PN} = "MIT & Apache-2.0"
+
:term:`SPDX_CUSTOM_ANNOTATION_VARS`
This option allows to associate `SPDX annotations
<https://spdx.github.io/spdx-spec/v2.3/annotations/>`__ to a recipe,
--
2.53.0
next prev parent reply other threads:[~2026-03-20 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 10:46 [PATCH v2 0/8] Update the documentation for 6.0 (Wrynose) Antonin Godard
2026-03-20 10:46 ` [PATCH v2 1/8] conf.py: define new {oecore,bitbake,meta_yocto}_rev roles Antonin Godard
2026-03-20 10:46 ` [PATCH v2 2/8] ref-manual/variables.rst: document qemuboot variables Antonin Godard
2026-03-20 10:46 ` [PATCH v2 3/8] ref-manual/variables.rst: SPDX_PACKAGE_URL: add missing parenthesis Antonin Godard
2026-03-20 10:46 ` [PATCH v2 4/8] ref-manual/variables.rst: document the LTO variable Antonin Godard
2026-03-20 10:46 ` Antonin Godard [this message]
2026-03-20 10:46 ` [PATCH v2 6/8] migration-guides: update 6.0 (Wrynose) release notes Antonin Godard
2026-03-20 10:46 ` [PATCH v2 7/8] docs-wide: add warning on disabled NPM fetcher Antonin Godard
2026-03-20 10:46 ` [PATCH v2 8/8] ref-manual/faq.rst: remove the CVS proxy note Antonin Godard
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=20260320-release-notes-6-0-v2-5-1bdb1eb142ae@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.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