Comment # 32 on bug 1226122 from Felix Miata

(In reply to Lukas Ocilka from comment #29)
> Created attachment 875434 [details]
> Bootloader settings
> 
> Guys, aren't you just picking the wrong bootloader choice? As the YaST team
> sees it, "Not Managed" means ... "not managed",

That depends on the meaning of "manage boot" I manage boot by configuring one
bootloader among 3, 13, 23 or however many distros on one machine (using
custom.cfg, in which stanzas are in the order I choose, in stanza quantity per
installed system I choose, with the labels I choose, among other stanzas that
load binaries not intended to load an installed OS). It really doesn't matter
who calls what what. 

> but if you select "Systemd
> Boot", then it should really select the package you wish and use systemd.

That one bootloader works because some bootloader is able to find boot files in
an expected location on some filesystem for each installed system in the
machine, most logically in a location identified as boot! Normally that meant
/vmlinuz (in openSUSE and various other distros) if a discrete filesystem, or
/boot/vmlinuz, 8 bytes or 13 bytes.

With BLS booting, we get e.g. /usr/lib/modules/1.2.3-4-default/vmlinuz, 41
bytes, not counting initrd's proportional increase, further bloating linu
lines, making it harder still to fit on one line along with UUID in an editor
window, or even fullscreen, or in a mailing list archive or forum post. It
poses a considerably increased opportunity for error in an admin's single
bootloader multiboot configuration management.

"Not managing" bootloader to me does not mean admin accidentally discovers he
needs to somehow determine how to get boot files into the expected location
within each of the 19 / or boot filesystems, something he did not need to do
previously. There's been a process for generations that gets boot files into
the boot file location even if a bootloader is not installed. That is now
broken because of an alternate boot location option which cannot be accounted
for in the boot setup part of the installer, while becoming an odd man out
among the 23 already installed OSes.

Given BLS booting is the new kid on the block, maybe the default can be
reverted to traditional by changing the alphabetic sort result by changing
package names to e.g.:
scriptlets-bl-aged
scriptlets-bl-newer