All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Making use of argp in GRUB utilities
Date: Fri, 26 Jan 2007 12:58:20 +0100	[thread overview]
Message-ID: <200701261258.20645.okuji@enbug.org> (raw)
In-Reply-To: <1169724331.3386.51.camel@pluto>

On Thursday 25 January 2007 12:25, Lubomir Kundrak wrote:
> I've noticed, that GRUB 2 uses argp in grub-emu [1], whereas other
> utilities use getopt_long [2]. Wouldn't it be nice to make this
> consistent?

Maybe. 

> I find the "GNU way," argp, approach more elegant, as demonstrated by a
> patch to util/i386/pc/grub-mkimage.c. Seeing a patch with more minuses
> than pluses is a good sign, indeed.
>
> The main argument against agrp framework could be, that non-GNU C
> libraries do not contain with it. There's a standalone libargp package
> [3] that is available for package systems of all major operating
> systems, including NetBSD and FreeBSD, so the only disadvantage is
> addding a dependency there.

I preferred that libargp would be included in our source tree so that it would 
be used when argp is not found in a system, but I guess Marco hasn't done it 
yet. This depends on which is more convenient for users, using an external 
shared library, or using our own. In GRUB Legacy, I included getopt for *BSD, 
and I got positive answers. So I feel that it would be better to include.

Okuji



  parent reply	other threads:[~2007-01-26 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 11:25 [PATCH] Making use of argp in GRUB utilities Lubomir Kundrak
2007-01-25 11:34 ` Lubomir Kundrak
2007-01-26 11:58 ` Yoshinori K. Okuji [this message]
2007-01-26 12:17   ` Lubomir Kundrak
2007-01-26 16:03     ` Marco Gerards
2007-01-26 18:42       ` Yoshinori K. Okuji
2007-01-26 16:01   ` Marco Gerards
2007-01-26 18:38     ` 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=200701261258.20645.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.