Skip site navigation (1) Skip section navigation (2)

Re: Release stamping (Was: [CORE] Schedule for release?)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)
Date: 2006-10-24 15:53:21
Message-ID: 200610241753.22003.peter_e@gmx.net (view raw or flat)
Thread:
Lists: 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.in
	sed '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/

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-10-24 16:05:58
Subject: Re: New CRC algorithm: Slicing by 8
Previous:From: Magnus HaganderDate: 2006-10-24 15:18:02
Subject: Further MSVC build updates

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group