Thread (26 messages) 26 messages, 8 authors, 2016-06-15

Re: [ALTERNATE PATCH] Add a simple option parser.

From: David Kastrup <hidden>
Date: 2016-06-15 22:43:39

"Medve Emilian-EMMEDVE1" [off-list ref] writes:
Hi Pierre,
quoted
-----Original Message-----
From: Pierre Habouzit [mailto:madcoder@debian.org] 
Sent: Friday, October 05, 2007 10:57 AM
To: Medve Emilian-EMMEDVE1
Cc: Mike Hommey; Kristian Høgsberg; git@vger.kernel.org; 
Junio C Hamano
Subject: Re: [ALTERNATE PATCH] Add a simple option parser.

On ven, oct 05, 2007 at 03:45:36 +0000, Medve Emilian-EMMEDVE1 wrote:
quoted
You probably already considered and rejected the GNU argp parser. I
used it before and I'd like to know reasons I should stay away from
it.
  Because it's GNU and that it's a heavy dependency to begin with.
So it's more of a political decision then a technical one?
Well, if it is GNU then it is likely to mean GPLv3 (or GPLv3+) at some
point of time, though it should certainly be possible for now to still
secure a v2-licensed version (either GPL or LGPL).

GNU also means a different coding and indentation style.

Personally, I couldn't care less about both points (I prefer the GNU
coding style anyway), but that's for the maintainer to decide, and one
also has to take into account the effect on developer motivation.

And the typical git developer AFAICT prefers to consider themselves as
unaligned with GNU and the FSF as much as possible.

-- 
David Kastrup
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help