From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix file name transformations (mostly)
Date: Tue, 15 Apr 2008 15:33:12 +0200 [thread overview]
Message-ID: <20080415133312.GE21548@thorin> (raw)
In-Reply-To: <1208211148.3971.38.camel@localhost.localdomain>
On Tue, Apr 15, 2008 at 12:12:28AM +0200, Lubomir Kundrak wrote:
> diff -urp grub-1.96.orig/util/update-grub.in grub-1.96/util/update-grub.in
> --- grub-1.96.orig/util/update-grub.in 2008-03-16 17:52:32.000000000 +0100
> +++ grub-1.96/util/update-grub.in 2008-03-16 17:59:42.000000000 +0100
> @@ -23,7 +23,7 @@ exec_prefix=@exec_prefix@
> sbindir=@sbindir@
> libdir=@libdir@
> sysconfdir=@sysconfdir@
> -grub_prefix=`echo /boot/grub | sed ${transform}`
> +grub_prefix=/boot/`echo /grub | sed ${transform}`
Is the second slash intentional?
> --- grub-1.96.orig/util/update-grub_lib.in.transform 2008-03-23 11:46:14.000000000 +0100
> +++ grub-1.96/util/update-grub_lib.in 2008-03-23 11:49:21.000000000 +0100
> @@ -95,7 +95,8 @@
> {
> # Prefer system path for space reasons (/boot/grub might be a very small
> # partition in case of OpenFirmware, etc).
> - for dir in ${pkgdatadir} /usr/share/grub /boot/grub ; do
> + for dir in ${pkgdatadir} ${pkgdatadir}/`echo grub | sed ${transform}` \
> + /boot/`echo grub | sed ${transform}`; do
I'd prefer is grub_prefix was defined here too (for readability).
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-04-15 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 22:12 [PATCH] Fix file name transformations (mostly) Lubomir Kundrak
2008-04-15 13:33 ` Robert Millan [this message]
2008-04-17 11:47 ` Lubomir Kundrak
2008-04-15 19:19 ` Pavel Roskin
2008-04-17 11:49 ` Lubomir Kundrak
2008-04-17 19:20 ` Pavel Roskin
2008-04-17 20:07 ` Robert Millan
2008-04-18 6:41 ` Lubomir Kundrak
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=20080415133312.GE21548@thorin \
--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.