Philip Martin <philip@codematters.co.uk> writes:
> Kevin Pilch-Bisson <kevin@pilch-bisson.net> writes:
>
> > I'm in favour of have a revnum in the version, but I don't really like the
> > idea of the build system crawling my entire wc and reading all of the entri
> es
> > files to see what revisions of files I have.
>
> I got as far as writing a program that did scan the working copy using
> svn_client_status. It took about 1-2 seconds to run on my not-so-fast
> machine. My vague plan was a build process something like:
>
> - build the libraries
> - build svnversion (my new program)
> - run svnversion to produce a C header file containing the version string
> - build svn with one file including the new header
>
> Version strings looked like
>
> 4231
> 4228:4231
> 4231M
> 4228:4231M
>
> for single revision, mixed revision, single revision modifed and mixed
> revision modified. It handled switched working copies as well.
>
> I never got as far as working out how to integrate it into the build
> system, or how to handle the regression tests that see the version
> number. I could dig it out if people are interested.
I think this would be a great idea. I'm tired of not having a version
number in my homegrown svn binaries due to the fear that my wc might
be mixed.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 11 01:53:58 2003