From: stondo@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: stondo@gmail.com, stefano.tondo.ext@siemens.com,
peter.marko@siemens.com, adrian.freihofer@siemens.com
Subject: [PATCH 2/4] spdx30_tasks: Add PURL generation for package identification
Date: Wed, 7 Jan 2026 19:09:48 +0100 [thread overview]
Message-ID: <20260107180951.140895-2-stondo@gmail.com> (raw)
In-Reply-To: <20260107180951.140895-1-stondo@gmail.com>
From: Stefano Tondo <stefano.tondo.ext@siemens.com>
Add automatic Package URL (PURL) generation according to the Yocto PURL
specification to enable package identification in vulnerability databases
and improve NTIA SBOM compliance.
Field added:
- software_packageUrl: Auto-generates Package URLs per Yocto PURL spec
Format: pkg:yocto/<LAYERNAME>/<BPN>@<PV>
See: https://github.com/package-url/purl-spec/pull/372
PURL Implementation:
- Type: yocto (official PURL type for Yocto recipes, per PR #372)
- Namespace: Layer name from FILE_LAYERNAME variable
- Name: BPN (base package name with prefixes/suffixes removed)
- Version: PV (package version from recipe)
- Normalization: Lowercase per PURL spec
New BitBake variable:
- SPDX_PACKAGE_URL: Override auto-generated PURL
The Yocto PURL type specification (purl-spec PR #372) has been approved
by the PURL maintainers and is ready for implementation. This follows
the agreed format from JPEWdev (Joshua Watt) and petermarko.
Signed-off-by: Stefano Tondo <stefano.tondo.ext@siemens.com>
---
meta/lib/oe/spdx30_tasks.py | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/meta/lib/oe/spdx30_tasks.py b/meta/lib/oe/spdx30_tasks.py
index f731a709e3..86430c7008 100644
--- a/meta/lib/oe/spdx30_tasks.py
+++ b/meta/lib/oe/spdx30_tasks.py
@@ -474,6 +474,36 @@ def create_spdx(d):
if val:
setattr(obj, name, val)
+ def generate_purl(d, package=None):
+ """
+ Generate Package URL (purl) for a package according to Yocto PURL spec.
+ Format: pkg:yocto/<LAYERNAME>/<BPN>@<PV>
+
+ See: https://github.com/package-url/purl-spec/pull/372
+ """
+ bpn = d.getVar("BPN")
+ pv = d.getVar("PV")
+
+ # Get layer name using FILE_LAYERNAME
+ # This is the correct variable that contains the layer name from BBFILE_COLLECTIONS
+ # (BBFILE_COLLECTIONS itself is not available outside of layer.conf)
+ layer = d.getVar("FILE_LAYERNAME")
+
+ if not layer:
+ layer = "core" # Default to core if layer detection fails
+
+ # For sub-packages, use BPN (base package name)
+ # Per spec: BPN has prefixes/suffixes removed
+ name = bpn
+
+ # Normalize name per PURL spec (lowercase only)
+ # Note: Underscores are not allowed in recipe names
+ name = name.lower()
+
+ purl = f"pkg:yocto/{layer}/{name}@{pv}"
+
+ return purl
+
license_data = oe.spdx_common.load_spdx_license_data(d)
deploydir = Path(d.getVar("SPDXDEPLOY"))
@@ -646,6 +676,10 @@ def create_spdx(d):
"software_packageUrl",
package=package
)
+ else:
+ # Auto-generate PURL if not manually specified
+ auto_purl = generate_purl(d, package)
+ spdx_package.software_packageUrl = auto_purl
pkg_objset.new_scoped_relationship(
[oe.sbom30.get_element_link_id(build)],
--
2.52.0
next prev parent reply other threads:[~2026-01-07 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 18:09 [PATCH] spdx-common: Clarify documentation and make SPDX_LICENSES extensible stondo
2026-01-07 18:09 ` stondo [this message]
2026-01-07 20:14 ` [OE-core] [PATCH 2/4] spdx30_tasks: Add PURL generation for package identification Joshua Watt
2026-01-08 11:14 ` Tondo, Stefano
2026-01-07 18:09 ` [PATCH 3/4] spdx30_tasks: Use recipe metadata for dependency PURL generation stondo
2026-01-07 18:09 ` [PATCH 4/4] spdx30_tasks: Add source package PURL support stondo
2026-01-07 18:09 ` [PATCH] spdx30: Add SBOM metadata component and supplier support stondo
2026-01-07 20:05 ` [OE-core] " Joshua Watt
2026-01-08 10:34 ` [PATCH] spdx30: Add supplier support for image and SDK SBOMs stondo
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=20260107180951.140895-2-stondo@gmail.com \
--to=stondo@gmail.com \
--cc=adrian.freihofer@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--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