Re: [COMMITTERS] pgsql: Preserve intermediate .c files in coverage mode - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Preserve intermediate .c files in coverage mode
Date
Msg-id 21072.1351632483@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Preserve intermediate .c files in coverage mode  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [COMMITTERS] pgsql: Preserve intermediate .c files in coverage mode  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On Sun, 2012-10-28 at 11:10 -0400, Tom Lane wrote:
>> [ blink... ]  I'd vote for making them precious all the time.  No such
>> behavioral change was discussed or agreed to,

> This is standard, default make behavior.  It only showed up here because
> the coverage processing doesn't list all the files it needs in make
> rules.

Yeah, I know it's "default", but it's not how our make files ever
treated these files before.  At the risk of repeating myself: a change
of this sort was not discussed nor agreed to.  And I'm not agreeing to
it.  I don't care for the idea that the build tree after a regular make
might not include all files that would be in a distribution tarball.

A concrete usage case that this breaks is doing something likefind . -name '*.c' | xargs grep whatever
Up to now I've always been able to assume that that would catch
occurrences of "whatever" coming from *.y and *.l files.  No more
though.  Maybe the derived *.c files are there, or maybe they're
not --- it'll be really history-dependent.

Please just make them precious.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Next
From: Christopher Browne
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL