[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: per-project version numbers - a way to support them? (without changing Subversion!?)

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-09-15 21:34:25 CEST

On 15-Sep-05, at 3:10 PM, Alan Jay Weiner wrote:

> Like others coming from other revision systems, I'm bothered by
> repository-wide
> version numbers. (I've accepted it, but it keeps coming up with
> clients - "why
> is this version X+N instead of X+1?")
> Just saying "get used to it" isn't an answer to those who don't
> *want* it to
> work that way.

Besides really having the urge to say "get used to it", I have to
wonder why you think revision numbers in your subversion repository
matter in the slightest? Why are your clients looking at the
revision numbers at all?

It's not like the numbers have any significant meaning. If the
number is 12 for one "version" on your project and "1345" for the
next, what does that really mean? The revision number getting bumped
doesn't correspond to any logical unit of change in the project, even
if you do have one revision number per project. E.g. it goes up even
when you revert a change and move backwards.

You can already get the version number of the last change to a folder/

$ svn info
Path: .
URL: svn://myserver/myproject/trunk
Repository UUID: bb17bfd5-26e3-0310-b67b-ca9ce5c526f2
Revision: 2788
Node Kind: directory
Schedule: normal
Last Changed Author: scott.palmer
Last Changed Rev: 2775
Last Changed Date: 2005-09-12 21:13:12 -0400 (Mon, 12 Sep 2005)
Properties Last Updated: 2005-04-29 16:51:32 -0400 (Fri, 29 Apr 2005)

Will "Last Changed Rev:" or perhaps some fancy script involving
finding the greatest " Last Changed Rev" in a tree get you want you

Is there a reason you can't use the one project per repository model?

> Ideas, anyone?

If you could explain the rational for needing subversion to track per-
project version numbers in the first place it might help generate
some ideas. I.e. why exactly is it that you don't want it to work
the way it does now? What problem are you trying to solve?
My first inclination would be to simply stop giving the revision
information to your clients... then they won't have anything to ask
questions about :).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 15 21:35:26 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.