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

Re: win32 version info

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: win32 version info
Date: 2004-07-29 14:58:07
Message-ID: 200407291658.07961.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-patches
Am Donnerstag, 29. Juli 2004 14:46 schrieb Magnus Hagander:
> 2) We'll *have* to start actually bumping at least minor versions
> whenever we change the code in a sharaed lib. Which we don't do now,
> except for libpq. For example, plperl still says 0.0, and plpgsql says
> 1.0. Also, all the conversion procs are at 0.0, and they all build from
> the same rule. That means they all need to get bumped when one of them
> changes. That may be a good idea for unix platforms as well, but it is
> more work during releases that has to be included. Not sure if we want
> to buy into that?

So far we haven't done any versioning on these because nothing checks their 
version.  If you think that now something is going to check their versions, 
then we're going to have to do something about that.  But what will happen if 
they stay at 0 indefinitely?

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

In response to

pgsql-patches by date

Next:From: Devrim GUNDUZDate: 2004-07-29 15:04:31
Subject: Updated Turkish FAQ
Previous:From: Magnus HaganderDate: 2004-07-29 14:55:32
Subject: Re: win32 version info

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