Re: Where to define the version number?

Greg Stein wrote:

>On Tue, Aug 06, 2002 at 02:47:07PM -0500, Karl Fogel wrote:
>
>>So:
>>
>>I'm wondering if svn_version.h is really the right place to define
>>these. If we did it in configure.in, then Art could use it, and it
>>would be easy to pass the same version information down to both
>>build.conf (which would become build.conf.in) and svn_version.h
>>(becomes svn.version.h.in).
>>
>>
>
>No can do. Windows does not use configure(.in), so you would end up defining
>the version number in configure.in *and* svn_private_config.hw.
>
>svn_version.h is the right place... that's why I put it there :-)
>

Thank you, Greg, for so gently giving them a piece of my mind. If *I*
had responded first, sparks would have flown. :-)

>>Whatever we do, I think it's important that there be exactly *one*
>>place where its defined. If svn_version.h can be that place, and
>>everyone else just deduces it from there, that's fine. I'm just
>>guessing that it would be easier if it were configure.in.
>>
>>
>
>Agreed on the "one place". I think we probably want to introduce
>SVN_VER_LIBRARY to contain the library version. We can then extract that for
>use in the Makefile for building libs.
>
>

I'm not sure I understand why the library version would be different
from SVN_VER_MAJOR. Changing the library version implies an incompatibla
ABI change, right? If that happens, eithre the the major or the minor
version number must be bumped.

Couldn't SVN_VER_LIBRARY just be $SVN_VER_MAJOR.$SVN_VER_MINOR?

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org