GRUB2 ships its extra data in /usr/lib, and "grub2-install" copies it to /boot. From that point on, we don't change it when the RPM changes. A user can still reinvoke grub2-install of course. And from a quick conversation with Peter Jones, we think this is the model we should use for all bootloaders. In other words, we need to: 1) Move the extlinux modules to /usr/lib 2) Change extlinux --update to copy them to /boot 3) Remove the %post from the spec file
(In reply to Colin Walters from comment #0) > And from a quick conversation with Peter Jones, we think this is the model > we should use for all bootloaders. All *BIOS* style bootloaders. That is, where installation to a disk is the immediate cause of activation.
Previous context to this for grub2 looks like: https://bugzilla.redhat.com/show_bug.cgi?id=735259 Ah ok, and for EFI we assume at the RPM installation time that /boot/efi is mounted, and have RPM itself write. In contrast again, gummiboot appears to ship its data in /usr/lib/gummiboot, and it has a %post to update the ESP. Would it make sense to sync those up and have grub2-efi have a %post to update the ESP? Or sync up with the BIOS path and only touch the ESP at installation time by default, and allow admins a tool to reinstall?
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.