From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Config file generation failure on Linux (gettext.sh)
Date: Sun, 3 Jan 2010 17:50:08 +0100 [thread overview]
Message-ID: <20100103165008.GG27698@thorin> (raw)
In-Reply-To: <4B3F52C1.6030201@labri.fr>
On Sat, Jan 02, 2010 at 03:05:53PM +0100, Grégoire Sutre wrote:
> You mean with an AC_PATH_PROG(GETTEXTBIN, gettext, echo) and substitute
> GETTEXTBIN in 10_linux?
Yes.
> But, in order to have a robust configuration script, it would still be
> desirable to check in 10_linux whether @GETTEXTBIN@ exists and revert to
> echo otherwise, wouldn't it?
As long as the script complains appropiately and exits non-zero if gettext
was installed, I would consider it robust (keep in mind grub.cfg isn't
touched at all unless all sub-scripts exit succesfuly).
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2010-01-03 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 15:01 Config file generation failure on Linux Grégoire Sutre
2010-01-01 12:03 ` Robert Millan
2010-01-02 14:05 ` Config file generation failure on Linux (gettext.sh) Grégoire Sutre
2010-01-03 16:50 ` Robert Millan [this message]
2010-01-03 16:55 ` Robert Millan
2010-01-03 23:16 ` Grégoire Sutre
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=20100103165008.GG27698@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.