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 v2 0/2] spdx30: Lifecycle scope variable declarations and test
Date: Sat, 21 Feb 2026 05:53:35 +0100 [thread overview]
Message-ID: <20260221045337.327402-1-stondo@gmail.com> (raw)
From: Stefano Tondo <stefano.tondo.ext@siemens.com>
This series adds bbclass variable declarations and a selftest for the
lifecycle scope dependency classification feature.
Depends on: [PATCH 00/14] spdx30: Enhance PURL generation and SBOM
metadata for SPDX 3.0.1
Changes since v1:
- Rebased on top of the PURL enhancement series (Series 1)
- Removed duplicate get_dependencies_by_scope() (already in Series 1)
- Fixed SPDX_CONCLUDED_LICENSE deletion (must not remove upstream code)
- Simplified test to use LifecycleScopedRelationship type directly
Stefano Tondo (2):
spdx-common: Declare SPDX_FORCE_*_SCOPE override variables
oeqa/selftest: Add test for lifecycle scope classification
meta/classes/spdx-common.bbclass | 13 ++++++++++
meta/lib/oeqa/selftest/cases/spdx.py | 39 ++++++++++++++++++++++++++++
2 files changed, 52 insertions(+)
--
2.53.0
next reply other threads:[~2026-02-21 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 4:53 Stefano Tondo [this message]
2026-02-21 4:53 ` [PATCH v2 1/2] spdx-common: Declare SPDX_FORCE_*_SCOPE override variables Stefano Tondo
2026-02-21 4:53 ` [PATCH v2 2/2] oeqa/selftest: Add test for lifecycle scope classification Stefano Tondo
-- strict thread matches above, loose matches on Subject: below --
2026-02-21 5:16 [PATCH v2 0/2] spdx30: Lifecycle scope variable declarations and test 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=20260221045337.327402-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