Re: Ignoring entries generated by autoconf in code tree

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Ignoring entries generated by autoconf in code tree
Date: 2015-03-25 14:34:06
Message-ID: 3648.1427294046@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(dot)paquier(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2015-03-25 15:46:25 Re: Error with index on unlogged table
Previous Message Peter Geoghegan 2015-03-25 13:55:14 varlena.c hash_any() and hash_uint32() calls require DatumGetUInt32()