[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gplv3 files and updates

From: Jim Meyering
Subject: Re: gplv3 files and updates
Date: Mon, 16 Jul 2007 09:00:32 +0200

Bruno Haible <address@hidden> wrote:
> Jim Meyering wrote:
>> consider what it means:
>> You prepare everything for a release, test to your heart's content,
>> and then at release time you rerun gnulib-tool to update copyright
>> notices.  Unfortunately, that might also pull in other (untested)
>> changes.  Of course, we can control that, but it is a potential
>> source of trouble.
> Just today, Patrick Leslie Polzer pointed us to the autogen.sh script used
> in findutils (mistakenly called 'import-gnulib.sh' although it does more than

"mistakenly"?  I prefer that name to "autogen.sh", since
the script has nothing to do with the GNU Autogen project:

> importing gnulib), see [1]. Look at the variable 'gnulib_version': If you set
> it to a date in the past, you eliminate this sort of trouble. And if you
> set it to 'HEAD', you track all changes like you currently do. If the
> coreutils 'bootstrap' script had the same configuration parameter, you would
> only - at some point before the release - change this variable from HEAD
> to the the current date, until after the release.

That sounds reasonable.
However, I'm not likely to make bootstrap do this in the next few weeks.
Are you?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]