From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] GNU GRUB program name transformations
Date: Fri, 26 Jan 2007 12:52:29 +0100 [thread overview]
Message-ID: <200701261252.29347.okuji@enbug.org> (raw)
In-Reply-To: <1169720852.3386.38.camel@pluto>
On Thursday 25 January 2007 11:27, Lubomir Kundrak wrote:
> From my point of view, the best solution was to use the autoconf macro
> AC_ARG_PROGRAM adding program name transformation options,
> --program-transform-name, --program-prefix and --program-suffix. Side
> effect of this is that it allows you to have multiple instances of GRUB
> 2 installed more comfortably.
I agree with this change. Thanks.
Besides the program names, you might want to change the path to which boot
images are installed, i.e. /boot/grub. As long as this directory is shared,
GRUB Legacy and GRUB 2 cannot coexist, well, at least not comfortably.
I sometimes wonder if it would be better to use a prefix "grub2-" instead of
"grub-" for GRUB 2 by default. GRUB Legacy and GRUB 2 are from the same
project GRUB, but they are fundamentally very different, so this might reduce
some confusion.
> The question is whether it is a good thing to transform program names by
> default in vendor specific packages (as is done with current version of
> pkgsrc package). Alternative solution would be to transform GRUB Legacy
> filenames, which, though it might cause some confusion to Legacy users,
> seems to be more appropropriate. Does GRUB Legacy support such
> transformations in its most recent version?
I suggest that you would not change GRUB Legacy for backward compatibility.
Okuji
prev parent reply other threads:[~2007-01-26 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 10:27 [PATCH] GNU GRUB program name transformations Lubomir Kundrak
2007-01-26 11:52 ` Yoshinori K. Okuji [this message]
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=200701261252.29347.okuji@enbug.org \
--to=okuji@enbug.org \
--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.