Eric Blake <ebl...@redhat.com> writes: > On 03/02/2011 10:40 AM, Matthew Booth wrote: >> I've just been trying to use getopt-gnu in a project, only to hit >> license confusion. The (LGPLv2+) project is already using a bunch of >> gnulib modules, which are all listed in a bootstrap file. Adding >> getopt-gnu to this list results in an incompatible license error. The >> module's license is given as 'LGPL'. > > Which means the most recent LGPL version (currently LGPLv3+). > >> The bootstrap script calls >> gnulib-tool with '--lgpl=2'. > > Which is why you got the license incompatibility warning. > >> >> Firstly, could the license please be updated to 'LGPLv2+', which I >> believe is probably the intention. > > Makes sense to me, since this is a module that syncs to glibc, and > glibc's version is LGPLv2+. Getting consent from the following authors > will make it even more legitimate (everyone listed as an author of any > commits to lib/getopt* since 2007-10-28, when LGPL was changed from > meaning LGPLv2+ to LGPLv3+ in the first place). > > Eric Blake - I consent > Bruno Haible > Jim Meyering > Simon Joseffson
Even if explicit agreement may not be needed here, it is fine with me. /Simon
