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

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Release stamping (Was: [CORE] Schedule for release?)
Date: 2006-10-24 21:24:22
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0FCC5@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> >> 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.
>
> > Right. And then you can only build from tarball and not
> from CVS, right?
>
> But isn't that true for borland already? We've got the .def
> files for libpq and the help-file for psql that we don't
> expect a borland environment to be able to build.

Borland, yes. MSVC, no. So I guess we could hav ethe MSVC bulid script
generate it for MSVC, and then stick it in the tarball for borland. It's
two different ways to do the same thing, but I guess we can do that..

//Magnus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2006-10-24 22:05:37 Re: [HACKERS] Replication documentation addition
Previous Message Dave Page 2006-10-24 21:06:41 Re: Release stamping (Was: [CORE] Schedule for