[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Licensing problem LGPLv3+ vs. GPLv2only conflict
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: Licensing problem LGPLv3+ vs. GPLv2only conflict |
Date: |
Mon, 29 Jul 2013 00:22:38 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7 |
On 07/28/2013 11:00 PM, Ludovic Courtès wrote:
>>> 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?
I understand the issue you are pointing out. What I am asking for is for
a practical solution to the issue. In theory --lpgl=2 would work, in
practice it cannot (for the reasons I pointed out before).
regards,
Nikos