From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: update-grub again (Re: ping (update-grub2))
Date: Wed, 11 Apr 2007 17:50:40 +0200 [thread overview]
Message-ID: <20070411155040.GA6722@aragorn> (raw)
In-Reply-To: <200611280826.48370.okuji@enbug.org>
On Tue, Nov 28, 2006 at 08:26:48AM +0100, Yoshinori K. Okuji wrote:
I'm terribly late at repliing here :-) - sorry about that. It's about lack of
time, not lack of interest.
> On Monday 27 November 2006 18:00, Robert Millan wrote:
> > No comments? Are you interested in getting this into the main grub tree?
> > In my opinion, since update-grub needs a rewrite it's a good oportunity to
> > merge this now and unify grub.cfg generation across distributions
> > (something that wasn't possible with the old update-grub because of
> > copyright issues).
> >
> > That said, if you don't like the idea then we could proceed adding it in
> > debian, but that might close the door to merging in the future (maintaining
> > the script in debian ourselves implies accepting contributions from many
> > people without any paperwork arrangements).
>
> I describe my own opinion. If others do not agree, let me know.
>
> If the script is generic enough, and other projects are willing to use it, it
> is convenient to put it in official versions ("official" means "upstream" in
> Debian, but I don't like the term "upstream" very much, BTW). So, in this
> case, I accept it. But if it is used only for Debian, I don't think it is
> worth doing.
The script is not Debian-specific in nature, and it can be used by other
distributors. Of course, since I wrote it in Debian it's not known to work
elsewhere, but there's nothing inherently unportable about it.
> I know it is not so nice to put distribution-specific scripts in official
> versions with my past experience, because official versions are not always
> synchronized with distribution versions, so when a script in an official
> version is "outdated" for a distribution, it is necessary to locally patch
> the script, and this effort can be quite painful, if you always need to make
> patches for every version.
>
> That's why we don't have the directory "debian" any longer. We had it in GRUB
> legacy in version 0.5.92 or something when Gordon was the maintainer of the
> GRUB package in Debian. But this became really annoying after Gordon got
> inactive, because I had no idea on how to maintain it, as I was not a Debian
> user then. And, someone (I think he was Jason Thomas) complained, and I
> decided to drop it from the official version.
I understand your concern. Shouldn't be a problem with update-grub IMHO.
If you're ok with it, I'll refurbish it into a patch against CVS so that you
can confirm the changes.
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next prev parent reply other threads:[~2007-04-11 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 10:18 update-grub2 Robert Millan
2006-10-15 10:40 ` update-grub2 Declan Naughton
2006-10-15 11:16 ` update-grub2 Robert Millan
[not found] ` <8764elkryd.fsf@neumann.lab.ossystems.com.br>
2006-10-16 13:48 ` update-grub2 Robert Millan
2006-11-27 17:00 ` ping (update-grub2) Robert Millan
2006-11-27 22:20 ` Vincent Pelletier
2007-04-11 15:57 ` update-grub again (Re: ping (update-grub2)) Robert Millan
[not found] ` <20061127214807.GA23613@linkinnovations.com>
2006-11-28 6:32 ` ping (update-grub2) Robert Millan
2006-11-28 7:26 ` Yoshinori K. Okuji
2007-04-11 15:50 ` Robert Millan [this message]
2007-04-17 12:49 ` update-grub2 patch Robert Millan
2007-04-17 13:26 ` Otavio Salvador
2007-04-21 13:38 ` Yoshinori K. Okuji
2007-04-29 23:22 ` Robert Millan
2007-05-01 20:45 ` Yoshinori K. Okuji
2007-05-02 13:31 ` Robert Millan
2007-05-02 15:35 ` Amin Azez
2007-05-03 15:48 ` Robert Millan
2007-05-03 21:44 ` Yoshinori K. Okuji
2007-05-04 7:14 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070411155040.GA6722@aragorn \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.