List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Tue, 26 Jun 2012 02:43:47 +0000 (UTC)
Duncan <1i5t5.duncan@...> wrote:
> Mike Gilbert posted on Mon, 25 Jun 2012 12:56:25 -0400 as excerpted:
> > On Mon, Jun 25, 2012 at 11:19 AM, Doug Goldstein <firstname.lastname@example.org>
> > wrote:
> >> Since Grub Legacy and Grub 2 are slotted, Portage won't remove the
> >> older version. Even if it removes the older one, everything
> >> necessary is installed into /boot and the MBR already.
> > Portage will remove the older slot the next time the user runs
> > emerge --depclean unless sys-boot/grub:0 is added to the world
> > file. I'm looking for a good way to communicate this to the user.
> > How about this: For ~arch, we do an ewarn in pkg_postinst if grub:0
> > is installed. For stable, we do a news item.
> Here's a bit of a different idea:
> Changing the bootloader is really a profile level change. If
> appropriate grub2-defaulted new profiles are created, and the old
> ones set to specify grub:0 as their default bootloader and then
> deprecated, this will automatically both provide the appropriate
> upgrade preparation required hint, and allow users to upgrade on
> their own schedule during the usual profile deprecation period.
No-no-no. I don't want profiles suddenly installing grub on my system.