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

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

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Release stamping (Was: [CORE] Schedule for release?)
Date: 2006-10-24 13:44:21
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D861@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackers
 

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
> Sent: 24 October 2006 14:30
> To: Dave Page
> Cc: pgsql-core(at)postgresql(dot)org
> Subject: Re: [CORE] Schedule for release? 
> 
> > In pgAdmin we have a simple bootstrap script the writes all 
> the version
> > numbers into a bunch of files, and then runs 
> automake/autoconf et al. It
> > sucks it out of one header which is all we have to modify manually.
> > Any reason we can't do something similar for PosgreSQL?
> 
> The pg_config.h.win32 file is intended to support building in an
> environment where you can't run automake/autoconf, or indeed much of
> anything else. 

That doesn't matter does it? Marc runs the bootstrap, which inserts the
version numbers into the right place and runs autoconf, then he commits
the changed files (configure, pg_config.h.win32 etc) to CVS. Only he (or
you or Bruce) should ever need to run it.

> Perhaps we could require Perl or something to be
> available?  I know Magnus is requiring Perl for his MSVC 
> build support.

Yes.

> This is getting offtopic for -core though.

Moved to -hackers...

Regards, Dave.

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-10-24 13:52:28
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)
Previous:From: Tom LaneDate: 2006-10-24 13:39:34
Subject: Re: [HACKERS] COPY does not work with regproc and aclitem

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