On 6/29/07, Karl Berry <[EMAIL PROTECTED]> wrote:
I am not sure how best to put GPLv3 and LGPLv3 into gnulib. I think that when projects update to GPLv3, the "COPYING" file should be GPLv3. But of course until the update, COPYING remains GPLv2.
Yes. gnulib will also need to update doc/gpl.texi and doc/gpl.txt. Similarly for doc/lgpl.texi and doc/lgpl.txt.
Maybe we should have doc/COPYINGv2 and doc/COPYINGv3 (ditto COPYING.LESSER) in gnulib, with no doc/COPYING at all, so the choice is explicit? Other ideas?
That seems reasonable to me at first. Projects which include gnulib code will need to slect one or the other because mixing the two is not possible, AIUI. James.
