All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Use getopt_long() instead of argp_parse() in grub-emu
Date: Sun, 18 Nov 2007 19:16:01 +0100	[thread overview]
Message-ID: <47408161.6020804@t-online.de> (raw)
In-Reply-To: <87tznjstll.fsf@xs4all.nl>

Marco Gerards wrote:
> Christian Franke <...> writes:
>
>   
>>> ...
>>>       
>> Will argp_parse() be a pre-requisite for building GRUB2 or will
>> argp-standalone be included (some other projects do) ?
>>     
>
> Personally, I would prefer it if it could be used as an external
> library.  The more we include, the more we need to care about.
>
>   

Yes, but then future package maintainers will have fewer portability 
issues to care about :-)


>> If you really want argp, why is it used only for the few trivial
>> options of grub-emu ? The other utils still use getopt_long().
>> grub-emu does not benefit much from argp, but introduces another
>> portability issue.
>>     
>
> It's what happened :-)
>
> Perhaps we should consider getopt_long, for now.  It's one file to
> change...  Does anyone else object?  Otherwise I'll review this patch.
>
>   

I would appreciate this.

Christian




  reply	other threads:[~2007-11-18 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10 15:26 [PATCH] Use getopt_long() instead of argp_parse() in grub-emu Christian Franke
2007-11-10 16:56 ` Marco Gerards
2007-11-10 21:45   ` Christian Franke
2007-11-18 11:04     ` Marco Gerards
2007-11-18 18:16       ` Christian Franke [this message]
2008-01-13 17:52 ` Marco Gerards
2008-01-14 21:37   ` Christian Franke
2008-01-15 11:13     ` Marco Gerards
2008-01-15 11:49       ` Robert Millan

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=47408161.6020804@t-online.de \
    --to=christian.franke@t-online.de \
    --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.