Re: lgpl compatible files archive?

[Jim Meyering]

Paul Eggert <address@hidden> wrote:
> Patrice Dumas <address@hidden> writes:
>
>> alloca malloc realloc strtod atexit dup2 getcwd getpagesize memmove memset
>> strerror regex
>
> These are mostly equivalent to existing and widely used LGPLed code,
> so I'd say they should be LGPLed.
>
> I would say the one exception is getcwd, where the code to support
> arbitrarily-deep nesting is not LGPLed anywhere that I can see.  For
> that case I would suggest adding a getcwd-lgpl module that omits the
> deep-nesting capability, much as we have already done (for similar
> reasons) with fts and fts-lgpl.
>
> Bruno, Jim -- do you have any objections to relicensing these?

Changing them from GPL to LGPL is fine with me.