Re: Ignoring entries generated by autoconf in code tree - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Ignoring entries generated by autoconf in code tree
Date
Msg-id 3648.1427294046@sss.pgh.pa.us
Whole thread Raw
In response to Ignoring entries generated by autoconf in code tree  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Ignoring entries generated by autoconf in code tree
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> When running autoconf from the root tree, autom4te.cache/ is
> automatically generated.
> Wouldn't it make sense to add an entry in .gitignore for that?

Personally, I don't want such a thing, as then I would tend to forget
to remove that cache file.  And you do want to remove it.  autoconf
goes pretty berserk if the cache file hangs around across significant
changes to configure.in, such as if you were to switch branches.
(Or at least that used to be true --- last time I got burnt by it
was quite some time ago, but possibly that's just because I'm careful
about removing the cache file.)

In short, -1.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: varlena.c hash_any() and hash_uint32() calls require DatumGetUInt32()
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: Error with index on unlogged table