Message-ID: <3A40F1B4.B2133F73@alumni.caltech.edu>
Date: Wed, 20 Dec 2000 17:51:48 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
Organization: Yes
MIME-Version: 1.0
To: Kovacs Zoltan Sandor <tip@pc10.radnoti-szeged.sulinet.hu>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	Dave Page <dpage@vale-housing.co.uk>, "'Joel Burton'" <jburton@scw.org>,
	Pgsql-interfaces@postgresql.org
Subject: Re: RE: version numbers of WinODBC
References: 
 <Pine.LNX.4.05.10012201541580.28983-100000@pc10.radnoti-szeged.sulinet.hu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> Is it possible to autogenerate the version numbers from PostgreSQL source
> configuration? I think the reason why the WinODBC driver has a separate
> version number is that it can be compiled directly using the
> src/interfaces/odbc/ directory only, so if someone wants to compile the
> DLL only, he/she can do it. By the way, if we support this (we must, of
> course), autogenerating version numbers doesn't seem to make sense, it
> must be set "by hand".

Since the cvs repository is now the "truth copy" of the code, the
standalone tarballs could be generated by a build process in
src/interfaces/odbc which explicitly finds and copies the current pgsql
version info. Once the tarball is built, then the version info travels
with the tarball. I'm not sure what the state of the standalone build is
at the moment; it used to work but I vaguely recall some discussion that
it was evil...

                     - Thomas