From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH 1/3] wic: locate systemd-boot efi files in buildchroot
Date: Tue, 30 Aug 2022 08:23:35 +0000 [thread overview]
Message-ID: <AS8PR10MB4865CCA43472CDEB15984EB789799@AS8PR10MB4865.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220822134750.44a99564@md1za8fc.ad001.siemens.net>
> -----Original Message-----
> From: Schild, Henning (T CED SES-DE) <henning.schild@siemens.com>
> Sent: Monday, August 22, 2022 1:48 PM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>
> Cc: isar-users@googlegroups.com; amikan@ilbers.de; Kiszka, Jan (T CED)
> <jan.kiszka@siemens.com>
> Subject: Re: [PATCH 1/3] wic: locate systemd-boot efi files in buildchroot
>
> Am Fri, 12 Aug 2022 08:50:37 +0200
> schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
>
> > This patch locates the systemd-boot efi files in the buildchroot and
> > not the target chroot.
> > By that, no imager-specifc dependencies have to be installed in the
> > target rootfs.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py
> > b/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py index
> > a24e04f3..7a65a98d 100644 ---
> > a/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py +++
> > b/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py @@ -415,9
> > +415,9 @@ class BootimgEFIPlugin(SourcePlugin): grub_cmd += "reiserfs
> > regexp " + grub_modules exec_cmd(grub_cmd)
> > elif source_params['loader'] == 'systemd-boot':
> > - kernel_dir = os.path.join(rootfs_dir['ROOTFS_DIR'],
> > "usr/lib/systemd/boot/efi/")
> > - for mod in [x for x in os.listdir(kernel_dir) if
> > x.startswith("systemd-")]:
> > - cp_cmd = "cp %s/%s %s/EFI/BOOT/%s" %
> > (kernel_dir, mod, hdddir, mod[8:])
> > + imager_efi_dir = "/usr/lib/systemd/boot/efi/"
> > + for mod in [x for x in os.listdir(imager_efi_dir) if
> > x.startswith("systemd-")]:
> > + cp_cmd = "cp %s/%s %s/EFI/BOOT/%s" %
> > (imager_efi_dir, mod, hdddir, mod[8:]) exec_cmd(cp_cmd, True)
>
> Reject! Touching a forked file will need that fix upstream first.
>
> Or (more likely) need to play with some variables to make that upstream
> code work. Check the diff between the fork and the original, and the commit
> history! The code looks a bit weird, the idea is to only insert a few lines here
> and there to hopefully be able to keep up with upstream more easily and
> avoid merge conflicts.
Before changing this, I checked the commit history of each line around that 😉
While your approach makes merging easier, changing things as you did before might break at runtime as variables are misused.
To give an example, have a look at [1].
There, you overwrite kernel_dir which is not a local variable (re-used in [2]) and which then points to a folder where no kernel is in.
Getting our customization into OE will also be hard as there the imager works differently.
I really prefer to let the code reflect the semantics instead of trying to make the fork as minimal as possible.
But I'm interested in others opinions as well.
Maybe Anton and Jan can comment.
Felix
[1] https://github.com/ilbers/isar/blob/master/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py#L439
[2] https://github.com/ilbers/isar/blob/master/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py#L449
>
> What you are proposing here is very much against that principle.
>
> Henning
>
> > else:
> > raise WicError("unrecognized bootimg-efi-isar
> > loader: %s" %
next prev parent reply other threads:[~2022-08-30 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 6:50 [PATCH 0/3] systemd-boot: Locate imager deps " 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 [this message]
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
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=AS8PR10MB4865CCA43472CDEB15984EB789799@AS8PR10MB4865.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@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