From: Lubomir Kundrak <lkundrak@redhat.com>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: The development of GRUB 2 <grub-devel@gnu.org>, okuji@enbug.org
Subject: Re: [PATCH] [UPDATE 2] More enhanced GNU GRUB program name transformations
Date: Tue, 13 Feb 2007 17:30:08 +0100 [thread overview]
Message-ID: <1171384208.17109.20.camel@pluto.brq.redhat.com> (raw)
In-Reply-To: <1171328483.518.49.camel@basalt>
Hi Hollis,
On Mon, 2007-02-12 at 19:01 -0600, Hollis Blanchard wrote:
> On Mon, 2007-02-12 at 00:20 -0600, Jerone Young wrote:
> >
> > This patch is derived from the patch sent earlier by Lubomir Kundrak.
> > What this patch adds is for library directories and directories in
> > /boot to be changed as well. So the user can easily launch
> >
> > ./configure --program-transform-name="s/grub/grub2/"
>
> This seems a little over-engineered to me. Why not just rename all the
> grub2 stuff to be "grub2-*" to begin with?
Do you think it is a good practice to rename the program names by
default? In my opinion is not the good place to tell what version of the
program the binary belongs to. This technique is commonly used to
separate versions of software when more than one version it is in use --
temporarily, till it gets wider acceptance. That's why I think it is
good that it is configurable. Additionally we merely use autoconf's
feature, not add or invent new stuff, so it hardly can be called
over-engineering.
> -Hollis
Regards,
--
Lubomir Kundrak (Red Hat Security Response Team)
next prev parent reply other threads:[~2007-02-13 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 6:20 [PATCH] [UPDATE 2] More enhanced GNU GRUB program name transformations Jerone Young
2007-02-13 1:01 ` Hollis Blanchard
2007-02-13 16:30 ` Lubomir Kundrak [this message]
2007-02-13 19:16 ` Hollis Blanchard
2007-02-14 10:38 ` Lubomir Kundrak
2007-02-14 20:12 ` Yoshinori K. Okuji
2007-02-17 22:39 ` Jerone Young
2007-03-05 2:35 ` Jerone Young
2007-03-05 17:06 ` Yoshinori K. Okuji
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=1171384208.17109.20.camel@pluto.brq.redhat.com \
--to=lkundrak@redhat.com \
--cc=grub-devel@gnu.org \
--cc=hollis@penguinppc.org \
--cc=okuji@enbug.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.