Devrim GÜNDÜZ <devrim at CommandPrompt.com> writes:
> (I think I raised this before, but I'm not sure)
>
> I see this line in configure.ac:
>
> m4_define([SLONREL_VERSION], esyscmd([echo "$Name: REL_1_2_STABLE $" | \
>
> Shouldn't it be REL_1_2_9 (or so) instead of this value? When I build
> packages, there is no minor version number in the spec...
>
> PostgreSQL's configure.in has the version number, like I proposed.

Hmm.  It'll only become REL_1_2_9 if you check out that particular
release.  And it becomes REL_1_2_10 when CVS gets tagged as such, and
a copy is checked out at that particular release level.

In the interim, I think it's probably right for the version to appear
to be REL_1_2_STABLE...  That's not actually a release...

Is there some other handling with PostgreSQL that simulates a release
number when checking out a major branch?
-- 
"cbbrowne","@","ca.afilias.info"
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)