[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Licensing problem LGPLv3+ vs. GPLv2only conflict
From: |
Ludovic Courtès |
Subject: |
Re: Licensing problem LGPLv3+ vs. GPLv2only conflict |
Date: |
Sun, 28 Jul 2013 23:00:26 +0200 |
User-agent: |
K-9 Mail for Android |
Nikos Mavrogiannopoulos <address@hidden> a écrit :
>On 07/20/2013 12:30 AM, Ludovic Courtès wrote:
>> Andreas Metzler <address@hidden> skribis:
>>
>>> There is another minor issue: gnulib.
>>
>> Normally one would specify the licensing constraints when importing
>> Gnulib modules, with --lgpl=2 in that case.
>
>Hello Ludo,
> Unfortunately that cannot be practically be used. It would require
>splitting into two gnulibs, one for the src/ directory and one for the
>lib/ directory. That would mean two copies of the same files, and twice
>the configure time checks. Given the (extremely large) number of checks
>gnulib adds to configure, that doesn't seem like a reasonable solution.
If GnuTLS is to be usable as LGPLv2, then --lgpl=2 must be used.
Otherwise you implicitly acknowledge that it's not v2 in actuality,
because you know you're possibly pulling v3 modules, no?
Ludo'.