automake-patches
[Top][All Lists]
Advanced

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

Re: [PATCH] {master} missing: do not touch timestamps; only warn for out


From: Eric Blake
Subject: Re: [PATCH] {master} missing: do not touch timestamps; only warn for out-of-date files
Date: Wed, 27 Jun 2012 15:43:11 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1

On 06/26/2012 04:32 AM, Bruno Haible wrote:
> Stefano Lattarini wrote:
>> I'm almost inclined not to do so, to force the affected
>> projects' broken setup to be fixed; i.e., if you are using Automake 1.11,
>> you let it install the correct 'missing' program, instead of forcing it
>> to use the 'missing' from Automake 1.13.
> 
> But developers don't have the impression that they are doing something
> wrong when they use an old 'missing' program.
> 

> 
> No warning. How is a developer meant to notice that he's doing something
> wrong if 'automake -Wall' does not tell him?

Unfortunately, the automake manual currently states that this behavior
of not warning about out-of-date scripts is already known (although I
argue that we should fix that part of the manual as part of fixing
automake to detect and warn when scripts are outdated):

>> Presently @command{automake} is able to diagnose situations where
>> @file{aclocal.m4} has been generated with another version of
>> @command{aclocal}.  However it never checks whether auxiliary scripts
>> are up-to-date.  In other words, @command{automake} will tell you when
>> @command{aclocal} needs to be rerun, but it will never diagnose a
>> missing @option{--force-missing}.


-- 
Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org



Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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