On Tue, May 14, 2013 at 04:38:34PM -0600, Eric Blake wrote:
On 05/14/2013 03:02 AM, Christophe Fergeau wrote:
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
The Free Software Foundation says:
https://www.gnu.org/licenses/gpl-howto.html
"You should also include a copy of the license itself somewhere in the distribution of your program. All programs, whether they are released under the GPL or LGPL, should include the text version of the GPL. In GNU programs the license is usually in a file called COPYING.
"If you are releasing your program under the LGPL, you should also include the text version of the LGPL, usually in a file called COPYING.LESSER. Please note that, since the LGPL is a set of additional permissions on top of the GPL, it's important to include both licenses so users have all the materials they need to understand their rights."
I don't think we need to make any changes to ship a copy of the GPL along COPYING.LIB.
That's where I think we've been wrong in the past. I'll work up a patch.
Ah I agree with you now, I had a look through the FAQ before sending this email looking for this kind of info and missed it :) Thanks for the explanation! Christophe