Re: ANN: Update to AdaGPGME and libgpg-error

[Andreas Almroth <andreasNO_XSPAM@almroth.com>]

Jeff C wrote:
> Andreas Almroth wrote:
> 
>> Hi all,
>>
>> For those of you interested, I have updated the Ada95 bindings to;
>>
>> * GPGME 1.0.2 (GnuPG Made Easy C API)
>> * libgpg-error 1.0 (common error message library for GnuPG components)
>>
<snip>
> 
> Nice!
> 
> One note..While I am a big fan of the GMGPL approach, it is not really 
> clear that it is entirely helpful in this case since GNUPG itself 
> appears to be GPL without exception...Not suggesting you need to change 
> the license binding but people using it (as always) need to understand 
> all of the license issues that are involved.
> 

Thanks!

Regarding the license, yes, it may not be entirely clear, I agree fully.
GnuPG is GPL only, GPGME is LGPL as its design is not limited to GnuPG, 
and in the future may include other backends that may use other 
licenses. I believe that could have been a reason why they choose LGPL.
I use GMGPL for most of my work that I publish. I like the GMGPL, it is 
an approved license, and is based on GPL with the exception that any 
code instantiating generics or using parts does not necessarily make the 
final product GPL/GMGPL. However copyrights are still in place.
GMGPL differs from LGPL, but to my understanding, not so much in reality.

In this specific scenario, it is hard to say where to draw the line, as 
GPGME, AFAIK, does not link to GnuPG, but merely calls the executable 
with the necessary arguments. AdaGPGME is then linking to GPGME and any 
resulting products would be based on LGPL, which means they can have 
other (even non-free) licenses. The GMGPL would not be in the way really.

Well, I'm not an legal eagle, but I don't see that GMGPL in any way is 
limiting/infringing LGPL.

Perhaps I should add a note to the README file...

/A