Re: [Xen-devel] [PATCH v4 09/15] autoconf: xen: force a refresh with autoconf

["Luis R. Rodriguez" <mcgrof@xxxxxxxx>]

On Mon, May 12, 2014 at 7:00 AM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> Luis R. Rodriguez writes ("Re: [Xen-devel] [PATCH v4 09/15] autoconf: xen: 
> force a refresh with autoconf"):
>> I spotted what I think is a bug on autoconf where I observed
>> inconsistent behaviour when you touch a file, sometimes it yielded
>> the results you wanted, sometimes it did not, in the end I got close
>> to linking the issue to the cache somehow, but before I dove myself
>> deeper into autoconf I found a force prevents this issue which let
>> me conserve some of the remaining sanity I have left. I'll follow up
>> with upstream autoconf on this eventually but figured providing all
>> the glory details on this on the commit log was not worth it. I'll
>> respin and add all the glory details.
>
> What are the downsides to the -f option ?  Do they apply in our
> situation ?  This needs to be discussed.
>
> (I haven't gone and read the autoconf manual; IMO this question ought
> to be answered, at least with a prima facie explanation, in the
> commit message.)

Other projects do it all the time, the impact is just that it will
take longer, I don't think that is an issue since this is an overhead
only incurred on developers and the maintainers. I'll try to verify
the bug I had mentioned and document it on the commit log but think
its pointless to wait on autoconf to get that fixed / verified before
we move on with -f considering other projects tend to use this.

  Luis

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel