Re: what's a "trail url"?

Jack Repenning <jrepenning@collab.net> writes:

> Somebody must like this behavior; any volunteers? How does it fit
> into your process? Seems like there's a sort of contradiction here: I
> run "svnversion" to learn what state the WC is in, but I need to know
> already what state it's in (or at least, what state I think it's in)
> in order to provide this parameter. Contradiction in terms. Chicken
> and egg. "I don't get it...."

svnversion is designed to provide the "version" of a working copy. It
was written to be used in things like build scripts, installation
scripts, Makefiles etc. For example Subversion's 'make install' runs
it and stores the result in include/subversion-1/svn-revision.txt.
Such scripts generally do know the URL with which they are associated.
For example, if we have a branch for 1.0 maintenance, the Makefile on
the branch may well change to use the branch URL rather than the trunk
URL.

svnversion is a separate executable, rather than an 'svn xxx' command,
because there was some talk of having it run during the build process
with the version being included in the final svn executable. Nothing
ever came of that.

I very rarely run svnversion by hand, I'm not really sure why people
do. When handling a working copy 'svn status' and 'svn info' are more
useful to me. Can you describe how you want to use svnversion?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org