Re: Release stamping (Was: [CORE] Schedule for release?) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Release stamping (Was: [CORE] Schedule for release?)
Date
Msg-id 200610241753.22003.peter_e@gmx.net
Whole thread Raw
In response to Re: Release stamping (Was: [CORE] Schedule for release?)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Why not?  The shipped tarball would contain exactly the same
> pg_config.h.win32 it does today; the only difference is that the
> version info would've been inserted automatically instead of
> manually.

I suggest you do it in a makefile as part of the distprep target.

distprep: pg_config.h.win32

pg_config.h.win32: pg_config.h.win32.insed 's/@VERSION@/$(VERSION)/g' $< >$@

maintainer-clean:rm -f pg_config.h.win32


That way we don't bother every configure runner with the issue.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)
Next
From: "Simon Riggs"
Date:
Subject: Re: New CRC algorithm: Slicing by 8