From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] create separate BOM for external initrd
Date: Wed, 27 Aug 2025 11:42:16 +0200 [thread overview]
Message-ID: <aK7S-Ar5mEqJF6lh@abai.de> (raw)
In-Reply-To: <20250804132243.1349594-1-felix.moessbauer@siemens.com>
On 2025-08-04 15:22, 'Felix Moessbauer' via isar-users 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.
We are back from the vacations, thanks for your patience.
Applied to next (capitalizing the title), thanks.
With kind regards,
Baurzhan
--
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/aK7S-Ar5mEqJF6lh%40abai.de.
prev parent reply other threads:[~2025-08-27 9:42 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
2025-08-27 9:42 ` Baurzhan Ismagulov [this message]
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=aK7S-Ar5mEqJF6lh@abai.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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