From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"Hillier, Gernot" <gernot.hillier@siemens.com>
Subject: Re: [PATCH 1/1] create separate BOM for external initrd
Date: Thu, 21 Aug 2025 12:27:50 +0000 [thread overview]
Message-ID: <6fa73f0a4741a21a01925bc90c690ecabff6aca3.camel@siemens.com> (raw)
In-Reply-To: <20250804132243.1349594-1-felix.moessbauer@siemens.com>
On Mon, 2025-08-04 at 15:22 +0200, Felix Moessbauer wrote:
> 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.
Hi, are there any blocking points, concerns, ...? Something I can do to
speedup the integration?
Best regards,
Felix
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/6fa73f0a4741a21a01925bc90c690ecabff6aca3.camel%40siemens.com.
next prev parent reply other threads:[~2025-08-21 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 13:22 'Felix Moessbauer' via isar-users
2025-08-21 12:27 ` 'MOESSBAUER, Felix' via isar-users [this message]
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=6fa73f0a4741a21a01925bc90c690ecabff6aca3.camel@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