James Youngman wrote:
> I enclose a patch which adds an option to gnulib-tool to modify the
> copyright banners of the Gnulib code to say "version 3". This allows
> projects which treat Gnulib files as generated code to import and
> reimport without reverting part of the source to GPL version 2. I
> propose to use this facility to allow findutils to migrate to GPL
> version 3 without needing lots of hand-editing every time I update
> gnulib from CVS.
Well, I hope we can get over this license change without adding complexity
to gnulib-tool. Complexity which might well be for historical reasons only,
in a month.
There is no problem with distributing a package whose README says
"GPLv3 or later" with some source files that say "GPLv2 or later", is there?
The sequence of events that I'm hoping for is this:
- First, get agreement that all projects that use gnulib are OK with GPLv3.
- Then, over a few weeks, let these projects upgrade their READMEs and
license notices in their source code.
- Then, change the license notices in gnulib's code.
Bruno
