Karl Fogel <kfogel@newton.ch.collab.net> writes:
> > +dnl AC_CONFIG_SRCDIR *required*; sanity-checks that the our src dir exists.
> > +AC_INIT([subversion], [0.14.0], [http://subversion.tigris.org])
> > +AC_CONFIG_SRCDIR(subversion/include/svn_types.h)
Two recent patches have revealed that we may need to change where we
define the version of Subversion.
Currently, the "master" location is svn_version.h, where we define the
SVN_VER_MAJOR, SVN_VER_MINOR, and SVN_VER_MICRO constants.
Then Art Haas posted a patch that would have duplicated this
information in configure.in. Meanwhile, Scott Lamb posted a patch
which hints that we (I *think*) are essentially duplicating the
SVN_VER_MAJOR constant in build.conf... Only it's out of sync right
now, claiming 1 instead of 0 :-). Greg Stein may clarify this, but
for now I'll assume that the situation is as I've just described it.
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).
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.
Thoughts?,
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 22:02:50 2002