update-grub2

Robert Millan rmh at aybabtu.com
Mon Oct 16 21:31:10 CEST 2006


On Mon, Oct 16, 2006 at 03:29:33PM -0200, Otavio Salvador wrote:
> Robert Millan <rmh at aybabtu.com> writes:
> 
> > [ Dropping CC to upstream for Debian-specific discussion ]
> >
> > On Mon, Oct 16, 2006 at 10:53:03AM -0200, Otavio Salvador wrote:
> >> >> It looks great! It's simple and flexible.
> >> >> 
> >> >> Robert, we could start to implement it on Debian side to start to grab
> >> >> "plugins" for other uses. We should also check what's the current
> >> >> feature set of update-grub and start a campain inside of Debian to
> >> >> grab the need "plugins" to don't have regressions for end user.
> >> >
> >> > I think we should wait to see what upstream (CCed) says.  If upstream GRUB
> >> > includes this feature, then it's an upstream issue for the other projects as
> >> > well.
> >> 
> >> Well, more or less.
> >> 
> >> If it's accepted by upstream, better! Otherwise we'll need to provide
> >> a upgrade path from Etch to Etch+1 and then we'll need something like
> >> that.
> >
> > There's not enough time..  I was thinking that we can release etch with the
> > current update-grub, and then prepare the replacement in etch+1.
> 
> I wasn't thinking about it's inclusion on etch but ...
> 
> > As for upgrade path, what do you mean?  To the user it's mostly the same.
> 
> Idenpendently of upstream accept or no your new update-grub wrapper,
> we'll need to support it to allow the user to upgrade from grub to
> grub2.

Ah, right.  I think we can postpone this untill grub2 becomes grub :)

-- 
Robert Millan

My spam trap is honeypot at aybabtu.com.  Note: this address is only intended for
spam harvesters.  Writing to it will get you added to my black list.



More information about the Pkg-grub-devel mailing list