https://bugzilla.novell.com/show_bug.cgi?id=782891 https://bugzilla.novell.com/show_bug.cgi?id=782891#c3 --- Comment #3 from Andrey Borzenkov <arvidjaar@gmail.com> 2012-10-20 09:22:56 UTC --- (In reply to comment #1)
Andrey,
You're right.
Please check out home:arvidjaar:bnc782891/grub2.devel_openSUSE_Factory. It builds grub2-efi with "grub2" transform. It still does not combine packages for two reasons - grub2-efi builds and installs \EFI\opensuse\grub.efi. What is it used for? It is created during build time so may not match user system at all and it is not referenced by anything after that. I really think it can be dropped. - grub2-efi pulls in egibootmgr. This probably is not needed on non-UEFI systems.
The tricky part is that we have many tools which manipulates grub2 settings with hard coded name (grub2-efi ..). They have to be sorted out in case they would break in the new package.
Afaics, the tools affected are wildly spread perl-bootloader , pm-utils, kiwi and other probably tools for configuring xen host
Package installs compatibility links for those commands used by perl-Bootloader and migrates configuration from /boot/grub2-efi into /boot/grub2 if current loader is grub2-efi. I have tested it for - update from previous version (migrating configuration) - update from updated version (just to make sure it does not do something funny) - switch from grub2-efi to elilo - switch from elilo back to grub2-efi Seems to work. I do not have possibility to test it in other environments.
And this implies YaST shouldn't have loader type grub2-efi.
It depends on whether you want to keep separate grub2-efi package. If yes, you need to know when perform bootloader refresh on update. Also UEFI is still sufficiently different so having is as separate loader type may prove useful. But that is something for YaST2 experts. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.