| 1 |
On Tue, 26 Jun 2012 02:43:47 +0000 (UTC) |
| 2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
| 3 |
|
| 4 |
> Mike Gilbert posted on Mon, 25 Jun 2012 12:56:25 -0400 as excerpted: |
| 5 |
> |
| 6 |
> > On Mon, Jun 25, 2012 at 11:19 AM, Doug Goldstein <cardoe@g.o> |
| 7 |
> > wrote: |
| 8 |
> >> Since Grub Legacy and Grub 2 are slotted, Portage won't remove the |
| 9 |
> >> older version. Even if it removes the older one, everything |
| 10 |
> >> necessary is installed into /boot and the MBR already. |
| 11 |
> > |
| 12 |
> > Portage will remove the older slot the next time the user runs |
| 13 |
> > emerge --depclean unless sys-boot/grub:0 is added to the world |
| 14 |
> > file. I'm looking for a good way to communicate this to the user. |
| 15 |
> > |
| 16 |
> > How about this: For ~arch, we do an ewarn in pkg_postinst if grub:0 |
| 17 |
> > is installed. For stable, we do a news item. |
| 18 |
> |
| 19 |
> Here's a bit of a different idea: |
| 20 |
> |
| 21 |
> Changing the bootloader is really a profile level change. If |
| 22 |
> appropriate grub2-defaulted new profiles are created, and the old |
| 23 |
> ones set to specify grub:0 as their default bootloader and then |
| 24 |
> deprecated, this will automatically both provide the appropriate |
| 25 |
> upgrade preparation required hint, and allow users to upgrade on |
| 26 |
> their own schedule during the usual profile deprecation period. |
| 27 |
|
| 28 |
No-no-no. I don't want profiles suddenly installing grub on my system. |
| 29 |
|
| 30 |
-- |
| 31 |
Best regards, |
| 32 |
Michał Górny |
Archives