cfs: Use bootupd for all installs if available#2327
Conversation
3e40503 to
f2eef01
Compare
Check if we have a new enough version of bootupd (by checking if the binary provides a `--bootloader` flag). If we have a new enough bootupd, use it to install grub-cc and systemd-boot We do not have this version of bootupd as an rpm package, so this will not break any existing systems. This is mostly for reverse dep testing in bootupd as testing this for bootc requires packaging bootupd, updating grub-cc and systemd-boot rpms to install their respective EFI binaries in the correct place which they don't right now Signed-off-by: Pragyan Poudyal <pragyanpoudyal41999@gmail.com>
f2eef01 to
edefd33
Compare
This isn't semantically equivalent though, bootupd always installs shim too, but the current direct bootc support for systemd-boot (intentionally) doesn't. This is kind of a gap in the flow today, as I think our Fedora-derivative examples still include the shim RPM. OK I just did redhat-cop/rhel-bootc-examples#18 |
yes, that's why this shouldn't affect the current flow, at least until we decide to make a new bootupd release. On that topic, we did have a discussion about a |
2 participants
Check if we have a new enough version of bootupd (by checking if the binary provides a
--bootloaderflag). If we have a new enough bootupd, use it to install grub-cc and systemd-bootWe do not have this version of bootupd as an rpm package, so this will not break any existing systems.
This is mostly for reverse dep testing in bootupd as testing this for bootc requires packaging bootupd, updating grub-cc and systemd-boot rpms to install their respective EFI binaries in the correct place which they don't right now