From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [OE-core][PATCH 0/5] Implement SPDX for deploy tasks
Date: Tue, 9 Jun 2026 16:15:51 -0600 [thread overview]
Message-ID: <20260609222331.1293007-1-JPEWhacker@gmail.com> (raw)
The SPDX use case for file system image has been well defined since SPDX
was first implemented, however there has always been a desire to also
express SPDX output for other non-image deliverables (primarily, those
that have a do_deploy task or similar). These types of tasks cannot
easily use the traditional method of having a separate SPDX task that
runs to create their SPDX output as this causes lots of problems with
the way dependencies are specified. Instead, it is desirable for these
tasks to directly produce SPDX output that can be consumed by other
tasks that depend on them.
This patch series adds support for this. Any sstate task can now be
added to the SPDX_DEPLOY_TASKS list and it will run a postfunc to
generate SPDX output that describes what is being deployed. For
classical do_deploy tasks, this is setup to be easy by automatically
capturing all the deployed output files in the SPDX data, but other
tasks can be added as well.
Finally, the do_create_image_spdx task is removed and replaced with a
SPDX deploy postfunc using this new system. This means that any task
that depends on do_image_complete will automatically also get the SPDX
output for the image, simplifying the dependency handling.
Joshua Watt (5):
classes/baremetal-image: Remove "do_" prefix from image manifest
spdx: Reformat
spdx: Add ability for deploy tasks to create SPDX
Add SPDX deploy tasks
spdx: Replace do_create_image_spdx with deploy task
meta/classes-recipe/barebox.bbclass | 3 +-
meta/classes-recipe/baremetal-image.bbclass | 2 +-
.../create-spdx-image-3.0.bbclass | 30 +-
meta/classes-recipe/deploy.bbclass | 1 +
meta/classes-recipe/devicetree.bbclass | 3 +-
meta/classes-recipe/kernel-fit-image.bbclass | 3 +-
meta/classes-recipe/kernel.bbclass | 3 +-
meta/classes-recipe/nospdx.bbclass | 2 +-
meta/classes/create-spdx-3.0.bbclass | 155 +++++++
meta/classes/spdx-common.bbclass | 2 +-
meta/lib/oe/sbom30.py | 52 ++-
meta/lib/oe/spdx30_tasks.py | 377 ++++++++++++++----
meta/lib/oe/spdx_common.py | 2 +-
meta/recipes-bsp/grub/grub-efi_2.14.bb | 3 +-
meta/recipes-bsp/opensbi/opensbi_1.8.1.bb | 3 +-
meta/recipes-bsp/u-boot/u-boot.inc | 3 +-
.../systemd/systemd-boot_259.5.bb | 4 +-
17 files changed, 509 insertions(+), 139 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-09 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 22:15 Joshua Watt [this message]
2026-06-09 22:15 ` [OE-core][PATCH 1/5] classes/baremetal-image: Remove "do_" prefix from image manifest Joshua Watt
2026-06-09 22:15 ` [OE-core][PATCH 2/5] spdx: Reformat Joshua Watt
2026-06-09 22:15 ` [OE-core][PATCH 3/5] spdx: Add ability for deploy tasks to create SPDX Joshua Watt
2026-06-09 22:15 ` [OE-core][PATCH 4/5] Add SPDX deploy tasks Joshua Watt
2026-06-09 22:31 ` Patchtest results for " patchtest
2026-06-10 6:17 ` Mikko Rapeli
2026-06-10 7:46 ` Richard Purdie
2026-06-09 22:15 ` [OE-core][PATCH 5/5] spdx: Replace do_create_image_spdx with deploy task Joshua Watt
2026-06-10 13:17 ` [OE-core][PATCH 0/5] Implement SPDX for deploy tasks Mathieu Dubois-Briand
2026-06-11 18:46 ` 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=20260609222331.1293007-1-JPEWhacker@gmail.com \
--to=jpewhacker@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox