Re: [Bug-gnulib] module maintainers

[Bruno Haible]

Paul Eggert writes:
> However, I see an item in your list that shouldn't be controversial,
> unless I'm misunderstanding your point.  gnulib caters to GNU
> application developers, who need GPLed code, not LGPLed code.

There are some modules, like alloca or vsnprintf, which GNU gettext
needs in LGPLed form, because they become part of a library that all
kinds of programs are encouraged to link with.

If you put the copy in gnulib under GPL, and you or anyone else make a
change to this copy, then this change is under GPL, and I cannot copy
the changed file to GNU gettext and put an LGPL header on it. Changing
a copyright from GPL to LGPL means relaxing some restrictions; only
the copyright holder can do it, which means I'd need to ask RMS each
time I copy such a file from gnulib to GNU gettext.

> This is for the convenience of gnulib users, who would
> otherwise have to replace the license themselves, and who would
> sometimes forget to do so in practice, leading to licensing glitches.

AFAIK there is no problem if you link an LGPL'ed .c file with one or
more GPL'ed ones, is there?

Bruno