Re: doc: Mention gnulib putenv module?

[Collin Funk]

Hi Bruno,

On 5/16/24 5:45 AM, Bruno Haible wrote:
> The way to deal with it, that is most consistent with the rest of Gnulib,
> is as follows:
> 
>   - Rename the 'putenv' module to 'putenv-gnu'.
> 
>   - Also change its description from:
>     putenv() function: change or add an environment variable.
>     to:
>     putenv() function: change, add, or remove an environment variable.
> 
>   - Rename the 'putenv-tests' module to 'putenv-gnu-tests'.
> 
>   - Add a new 'putenv' module that is merely an indirection to 'putenv-gnu'
>     (for backward compatibility, in order not to break coreutils, gcal, guile,
>     octave, etc.). In the NEWS file mention
>        2024-MM-DD  putenv          This module is renamed to 'putenv-gnu'.

Thanks for the guide. Should I update occurrences of 'putenv' to
'putenv-gnu' in dependencies and then mark 'putenv' with the
'obsolete' status? That way './bootstrap' will print a small warning
letting people know to change it eventually.

Collin