RPM Community Forums

Mailing List Message of <popt-devel>

Re: Cloning getopt (and getopt_long) into popt?

From: Jeff Johnson <n3npq@mac.com>
Date: Sat 20 Dec 2008 - 15:25:01 CET
Message-id: <A0684C38-6CC6-4B59-A037-C55E81714E8D@mac.com>

On Dec 20, 2008, at 3:06 AM, Ralf S. Engelschall wrote:

>
> Ah, yes, as long as one can still build a POPT without these two  
> symbols
> (to avoid conflicts) this would be a really nice addition for POPT. I
> would say: go for it as long as is an _optional_ feature!
>

I should likely state the underlying reason as well, adding persistent
configurable default option settings.

Both popt/getopt_long have a means to configure options persistently.

However, popt alias/exec attach to executables, while getopt_long can  
save
option values (and presence) in a state file to be parsed.

wget (and iirc gnupg) have functionality captured in ~/.foo file
parse that is not easily/cleanly replicated with alias/exec.

todo+= (with disabler) but it will likely be a while before I
get back to studying rpmwget.c needs.

73 de Jeff

  • application/pkcs7-signature attachment: smime.p7s
Received on Sat Dec 20 15:26:50 2008
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.