Re: GPLv3 re-licensing

[Simon Josefsson]

Jim Meyering <address@hidden> writes:

> Simon Josefsson <address@hidden> wrote:
>
>> How about this?
>>
>> I haven't been following the re-licensing discussions closely (still
>> catching up), but these files seems to be used during the build phase,
>> and using the GPLv3 for that seems non-controversial, or?
>>
>> Btw, libidn 1.0 (recently released) uses latest gnulib, and there were
>> no license problems.  I'm doing the same exercise now with gsasl, but it
>> seems there are no conflicts there either.
>>
>> /Simon
>>
>> Index: ChangeLog
>> ===================================================================
>> RCS file: /sources/gnulib/gnulib/ChangeLog,v
>> retrieving revision 1.1872
>> diff -u -p -r1.1872 ChangeLog
>> --- ChangeLog        31 Jul 2007 22:34:58 -0000      1.1872
>> +++ ChangeLog        6 Aug 2007 13:55:04 -0000
>> @@ -1,3 +1,7 @@
>> +2007-08-06  Simon Josefsson  <address@hidden>
>> +
>> +    * build-aux/maint.mk, build-aux/GNUmakefile: Relicense to GPLv3+.
>
> Thanks.  Please commit.

Done.

> I've already converted to GPLv3+ the files in coreutils
> from which those are derived.

Any chance we could merge these?  My idea with maint.mk was that it only
contains generic rules no, and if you need project-specific rules,
you'll add them.  Thus, CoreUtils Makefile.maint could contain:

include maint.mk

and we could start merging rules?

It is not a high priority project though...

/Simon