public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	gernot.hillier@siemens.com, cedric.hombourger@siemens.com
Subject: [PATCH 1/1] create separate BOM for external initrd
Date: Mon,  4 Aug 2025 15:22:43 +0200	[thread overview]
Message-ID: <20250804132243.1349594-1-felix.moessbauer@siemens.com> (raw)

The BOM (manifest file) describes all packages installed in a rootfs.
Currently, the BOM is just generated for the images rootfs, but not for
the initrd. This is fine, as long as no separate initrd is used. Tests
on isar-cip-core have shown, that ~4-10 source packages are only
referenced by the initrd rootfs, but not by the image rootfs.

We change this by generating the BOM also for the rootfs of external
initrds. Note, that this has a significant overlap with the images
rootfs, as it also contains all essential packages. As there is
currently no way to explain in a uniform BOM which components are used
where, the merging of the BOMs is left to the user.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
I plan so send a similar patch to the SBOM RFC series as well.

Best regards,
Felix

 meta/classes/initramfs.bbclass | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/classes/initramfs.bbclass b/meta/classes/initramfs.bbclass
index 3a996f78..658ef0ac 100644
--- a/meta/classes/initramfs.bbclass
+++ b/meta/classes/initramfs.bbclass
@@ -18,10 +18,14 @@ INITRAMFS_INSTALL += "${@ ("linux-image-" + d.getVar("KERNEL_NAME")) if d.getVar
 # Name of the initramfs including distro&machine names
 INITRAMFS_FULLNAME = "${PN}-${DISTRO}-${MACHINE}"
 
+# Bill-of-material
+ROOTFS_MANIFEST_DEPLOY_DIR = "${DEPLOY_DIR_IMAGE}"
+ROOTFS_PACKAGE_SUFFIX = "${INITRAMFS_FULLNAME}"
+
 DEPENDS += "${INITRAMFS_INSTALL}"
 
 ROOTFSDIR = "${INITRAMFS_ROOTFS}"
-ROOTFS_FEATURES = ""
+ROOTFS_FEATURES = "generate-manifest"
 ROOTFS_PACKAGES = "initramfs-tools ${INITRAMFS_PREINSTALL} ${INITRAMFS_INSTALL}"
 
 inherit rootfs
-- 
2.50.1

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20250804132243.1349594-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2025-08-04 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 13:22 'Felix Moessbauer' via isar-users [this message]
2025-08-21 12:27 ` 'MOESSBAUER, Felix' via isar-users
2025-08-27  9:42 ` Baurzhan Ismagulov

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=20250804132243.1349594-1-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=gernot.hillier@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