From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: christoph.steiger@siemens.com, cedric.hombourger@siemens.com,
quirin.gylstorff@siemens.com, jan.kiszka@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [RFC PATCH 0/3] Create uniform manifest file
Date: Fri, 10 Oct 2025 17:12:02 +0200 [thread overview]
Message-ID: <20251010151205.2122000-1-felix.moessbauer@siemens.com> (raw)
The .manifest file contains the list of installed packages, along with their
binary -> source package relations. We recently added support to generate
the manifest also for an external initrd rootfs, however support for the
imager was still missing.
This series adds this support and also creates a uniform manifest file for
all components in the .wic image. As the imager dependencies cannot be
tracked precisely in an automated way (the IMAGER_INSTALL contains tooling
as well as artifacts which are copied into the image), we add a new variable
IMAGER_BOM to define the set of packages that should end up in the BOM.
The RFC implements this support for the .manifest file. Later on, a similar
approach can be implemented for the SBOM.
Best regards,
Felix Moessbauer
Siemens AG
Felix Moessbauer (3):
Add support to add imager dependencies to BOM
wic: create uniform manifest describing all image components
qemuamd64: add IMAGER_BOM entries
doc/user_manual.md | 1 +
meta-isar/conf/machine/qemuamd64.conf | 1 +
meta/classes/image-tools-extension.bbclass | 7 +++++++
meta/classes/image.bbclass | 6 ++++++
meta/classes/imagetypes_wic.bbclass | 4 ++++
5 files changed, 19 insertions(+)
--
2.51.0
--
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/20251010151205.2122000-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2025-10-10 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 15:12 'Felix Moessbauer' via isar-users [this message]
2025-10-10 15:12 ` [RFC PATCH 1/3] Add support to add imager dependencies to BOM 'Felix Moessbauer' via isar-users
2025-10-10 15:12 ` [RFC PATCH 2/3] wic: create uniform manifest describing all image components 'Felix Moessbauer' via isar-users
2025-10-10 15:12 ` [RFC PATCH 3/3] qemuamd64: add IMAGER_BOM entries 'Felix Moessbauer' via isar-users
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=20251010151205.2122000-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@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