On Tue, May 07, 2013 at 10:48:25AM -0600, Eric Blake wrote: > Hmm. I just noticed that our COPYING file is the older copy of > COPYING.LIB (LGPL); but LGPL requires that we distribute a copy of the > GPL (since the LGPL refers by reference to terms from the GPL). Looks > like we still have some more work to do in this area. configure.ac copies COPYING.LIB to COPYING, COPYING is not stored in git: # Only COPYING.LIB is under version control, yet COPYING # is included as part of the distribution tarball. # Copy one to the other, but only if this is a srcdir-build. # You are unlikely to be doing distribution-related things in a non-srcdir # build test "x$srcdir" = x. && ! test -f COPYING && cp -f COPYING.LIB COPYING I can send a patch removing that bit from configure.ac and adding a GPLv2 COPYING file, however - this is the first time I hear about such a requirement for LGPLv2 licensed-code - I didn't see references to terms from the GPL in the LGPL license, it's only referenced as a whole there: 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. I don't think we need to make any changes to ship a copy of the GPL along COPYING.LIB. Christophe
Attachment:
pgpvTzzxsLSI_.pgp
Description: PGP signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list