public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: isar-users@googlegroups.com, amikan@ilbers.de, jan.kiszka@siemens.com
Subject: Re: [PATCH 0/3] systemd-boot: Locate imager deps in buildchroot
Date: Mon, 22 Aug 2022 13:55:58 +0200	[thread overview]
Message-ID: <20220822135558.4a4a3f91@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220812065040.1580962-1-felix.moessbauer@siemens.com>

Am Fri, 12 Aug 2022 08:50:36 +0200
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:

> This patch reworks the logic how we create images with systemd-boot:
> Instead of installing the systemd-boot dependency into the target
> image, we install it in the buildchroot, leveraging the IMAGER_INSTALL
> infrastructure.
> 
> This has the following advantages:
> 
> - smaller images: The systemd-boot package is no longer installed
> into the image
> - unified imager logic with OE

Good idea. You could also look at my last series of bumping wic and
reforking all the bootloader bits, enabling systemd-boot in the first
place.

That bootloader used to stick out because it was the only one to install
"from withing inside the target rootfs", as opposed to "from outside".

systemd itself is very likely to be installed there and the bootloader
used to be a part of that main package. But with >11 it has been split
out into its own package, so indeed even if the target runs systemd we
might not need to install that package. In fact we could probably even
use systemd-boot for a system using openrc or sysvinit.

I do not remember all the details.

But i do remember that i actually wanted to eventually move all
bootloaders to "inside" and maybe even drop support for "outside". That
would be to enable kernel updates in isar generated images.
And if one wanted boot loader updates the bootloaders would also have
to become part of the target install set.

regards,
Henning

> Best regards,
> Felix
> 
> Felix Moessbauer (3):
>   wic: locate systemd-boot efi files in buildchroot
>   Rework imager support for systemd-boot
>   Install systemd-boot into buildchroot for qemuarm
> 
>  meta-isar/conf/multiconfig/qemuarm-bookworm.conf        | 2 +-
>  meta/conf/distro/debian-common.conf                     | 6 +++---
>  meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py | 6 +++---
>  3 files changed, 7 insertions(+), 7 deletions(-)
> 


      parent reply	other threads:[~2022-08-22 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  6:50 Felix Moessbauer
2022-08-12  6:50 ` [PATCH 1/3] wic: locate systemd-boot efi files " Felix Moessbauer
2022-08-22 11:47   ` Henning Schild
2022-08-30  8:23     ` Moessbauer, Felix
2022-08-30 15:06       ` Henning Schild
2022-08-12  6:50 ` [PATCH 2/3] Rework imager support for systemd-boot Felix Moessbauer
2022-08-12  6:50 ` [PATCH 3/3] Install systemd-boot into buildchroot for qemuarm Felix Moessbauer
2022-08-12  7:08 ` [PATCH 0/3] systemd-boot: Locate imager deps in buildchroot Bezdeka, Florian
2022-08-12  7:17   ` Moessbauer, Felix
2022-08-22 11:55 ` Henning Schild [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=20220822135558.4a4a3f91@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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