Remove grubby from core, enable systemd-boot installs
With the advent of alternative bootloaders (systemd-boot) whether or not grubby gets installed should be dependent on whether grub is selected as the bootloader. This currently happens correctly with anaconda and the grub dependencies, so it can be removed safely. That allows systemd-boot to be installed cleanly without grubby drippings confusing it. While anaconda may now request sdubby and systemd-boot, i'm told the comment in the anaconda section isn't 100% accurate as anaconda may try to install all those selections to the live images. So, lets not add those to the anaconda comps yet. Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
This commit is contained in:
parent
d89e158a76
commit
3e5589fc5a
|
@ -75,6 +75,7 @@
|
|||
<packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">grub2-tools</packagereq>
|
||||
<packagereq arch="x86_64" type="mandatory">grub2-tools-efi</packagereq>
|
||||
<packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">grub2-tools-extra</packagereq>
|
||||
<packagereq type="mandatory">grubby</packagereq>
|
||||
<packagereq type="mandatory">hfsplus-tools</packagereq>
|
||||
<packagereq type="mandatory">iscsi-initiator-utils</packagereq>
|
||||
<packagereq type="mandatory">kbd-legacy</packagereq>
|
||||
|
@ -649,7 +650,6 @@
|
|||
<packagereq type="mandatory">e2fsprogs</packagereq>
|
||||
<packagereq type="mandatory">filesystem</packagereq>
|
||||
<packagereq type="mandatory">glibc</packagereq>
|
||||
<packagereq type="mandatory">grubby</packagereq>
|
||||
<packagereq type="mandatory">hostname</packagereq>
|
||||
<packagereq type="mandatory">iproute</packagereq>
|
||||
<packagereq type="mandatory">iputils</packagereq>
|
||||
|
|
Loading…
Reference in New Issue