Re: svn --version should give: 0.15.0 (build <revision>)

cmpilato@collab.net wrote:
>
> solo turn <soloturn99@yahoo.com> writes:
>
> > could you please add the revision to the output of the --version
> > command?
>
> Not really. I often have a mixed working copy with countless
> different revisions of different files. There is no one version
> number that accurately describes the contents of my compilation.

I'm +1 on the revision in the build number.

A couple of thoughts to what you said.

One, I think most people that install and use Subversion in a
production environment would use single revision source trees.

I'm guessing that mostly its the Subversion development team that
uses revision copies. And then even, do mixed revisions get
installed for use? I know I don't install them, but just test
them. I make my changes, run make check and when I'm happy with
it, I check it in and then build the production svn off of that.

We can make the build process smart enough to look through the
source tree for the revisions of the source files and place them
in the build number. So you could get "build 0.15.0 (revs 3643,
3656, 3800)". If there is more than one revision, then it's clearly
a mixed rev tree and it'll take a closer look to see which files are
at the different revisions. If the rev is a single number, then
its easy to see where it came from.

So for most people, I think having a single number would be good.
For those people who run mixed revisions, they already know they
have a mixed rev.

Finally, I think there's a lot more users of svn then developers
(or we hope there will be in the future) and single rev trees
will be the norm.

Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org