https://bugzilla.suse.com/show_bug.cgi?id=1208117 https://bugzilla.suse.com/show_bug.cgi?id=1208117#c6 --- Comment #6 from Martin Wilck <martin.wilck@suse.com> --- (In reply to Franck Bui from comment #5)
I can send a PR if it makes things easier for you.
Yes, please. I've digged around a bit; it seems to me that /boot/efi/loader/loader.conf would be the configuration file to check for, but that file doesn't have to exist. At least one boot loader entry would need to exist, I suppose; but those will be rather difficult to locate correctly from the scriptlets. IIUC the boot loader entry would have a distribution-specific name; I still have to understand that part (short explantion welcome). Perhaps we should check for the existence of "/usr/bin/bootctl"?
However at a first glance it would have been better if `run_bootloader()` didn't > make any assumption on the supported bootloaders and let /usr/lib/bootloader /bootloader_entry figure out itself what to do with the current installation.
Not sure about this. I assume the run_bootloader() test exists for a reason. Maybe in order to allow a setup where just no bootloader related scripts are run? This goes back all the way to openSUSE 10 (https://bugzilla.suse.com/show_bug.cgi?id=303734). At least we'd need to test if bootloader_entry handles the absence of any configuration files gracefully. -- You are receiving this mail because: You are on the CC list for the bug.