On 07/29/2010 02:35 PM, Bruno Haible wrote: > Adam Stokes wrote: >> Is it possible to change these modules licenses to LGPLv2+? > > Have you considered releasing your library under LGPLv3+? > > For your request, the following contributors since 2007-10-07 > would have to agree: > > Module Source file Contributors > ------ ----------- ------------ > > chown lib/chown.c Eric Blake > > lchown lib/lchown.c Eric Blake > > open lib/open.c Eric Blake, Bruno Haible
How did you come up with this list? Or more generally, what's the easiest way to check whether a list of modules meets a certain license restriction? I know that --lgpl=2 works when using --import into an existing project, but it didn't seem to do a thing when I tried: $ ./gnulib-tool --with-tests --create-testdir --dir=testdir1 --lgpl=2 lchown I was expecting that to abort with a complaint about incompatible modules. I also tried: $ ./gnulib-tool --extract-license `./gnulib-tool --extract-dependencies lchown chown open` but that doesn't tell which modules have the problems, just whether there are any that aren't LGPLv2+. -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
