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

Re: Current Updated Revision Number

From: Jack Repenning <jrepenning_at_collab.net>
Date: 2003-09-08 21:20:04 CEST

At 8:11 PM +0100 9/8/03, Julian Foad wrote:
>> cd trunk/ # or branches/whatever, or ....
>> svn up -r 1234 # includes conf/revfile, so it gets 1234
>> svn up -r 2345 src # excludes conf/revfile, so it doesn't change?
>>Now revfile says "1234", but svnversion on "." would say
>>"1234:2345", which I think is not what anyone would want.
>That is just the same as if you had a manually maintained
>"VERSION.TXT" file in the root of the project, and updated only a
>sub-tree. VERSION.TXT would be out of date. If you put VERSION.TXT
>in the sub-tree, then it would have been updated ... regardless of
>whether it was manually maintained or using this new keyword. The
>system works exactly as designed and as expected. I think that is
>reasonable behaviour.

Depends on what "manually maintained" means.

The system that seems sensible to me is to compute the version info
(i.e., run svnversion) at the time you build the system (or otherwise
decide it's final, whatever that means if it's a directory tree that
doesn't get "built"). So, if there's a makefile, you might use
"REV=`svnversion`", and possibly a forcing production to ensure that
one file is rebuilt whenever you build anything. Or, if it's a web
tree, then the script you use to export it to the htdocs directory
would also run "svnversion > VERSION.TXT".

Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 8 21:22:20 2003

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.