Hi, to give some background: The value for perl-Bootlader was to shield the fact that we support multiple different bootloaders from YaST, as well as various scripts (e.g. kernel post-install script). Withe the move to GRUB2 as the only supported bootloader - on all architectures (well, it is not always exactly the same, but it is configured the same way), this layer is not necessary any more. Since it was very complex, it also came with its portion of entries in our bzilla. With calling GRUB directly and focusing on a single bootloader, the whole stack got much simpler, which, after some initial tuning, will hopefully reduce the bug load. Jiri On 10.5.2016 07:35, Ancor Gonzalez Sosa wrote:
While looking at another problem I notice that in TW YaST2 Bootloader module appears to call grub2-install directly, instead of calling perl-Bootloader. Not only that, but it also called grub2-install where there was *no* change in bootloader location, so simple grub2-mkconfig would be sufficient. Is it intentional? This looks like step backward, actually. Dropping perl-Bootloader and calling grub2-install and grub2-mkconfig
On 05/10/2016 05:36 AM, Andrei Borzenkov wrote: directly is intentional. There are plans to drop perl-Bootloader from the distribution entirely.
About the extra call to grub2-install, is it harmful?
Cheers.
-- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org