Re: Licensing problem LGPLv3+ vs. GPLv2only conflict

[Nikos Mavrogiannopoulos]

On 07/24/2013 08:53 AM, Andreas Metzler 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.
> 
> How about doing a dummy import with --lgpl=2 for all modules used by
> the library?

It seems that isn't viable either and a separation (or complete drop of
non-lgplv2 parts of gnulib) will be necessary. There is no guarantee
that code for something irrelevant (e.g., printf) isn't included in the
library.

What would be ideal, is for gnulib to generate multiple libraries based
on the license of their contents. That way one would only need a single
copy of the library source files and just link to the appropriate .a.

regards,
Nikos