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

RE: Re: working-revision keyword

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Wed, 3 Sep 2008 09:53:17 -0500

> -----Original Message-----
> From: Lixuesong [mailto:givemenews_at_tom.com]
> Sent: Wednesday, September 03, 2008 5:13 AM
> To: Roth, Pierre
> Cc: users_at_subversion.tigris.org
> Subject: Re: working-revision keyword
> the way descripted in FAQ "Why doesn't the $Revision$ keyword do what
> want? It expands to the file's last-changed revision, but I want
> something that will expand to the file's current revision."
> is not ideal since it depends on svn command 'svnversion'.
> if I compile source code in a machine which no svn installed, the
> compile will fail since it doesn't know what is svnversion.

What you're asking for isn't practical. You would have to manually run
a command to walk the tree and update the keywords in every file. This
would have the side effect of changing every file, which would cause all
files to be rebuilt.

Instead, your build process should pull code by revision number and put
the revision number in a file (ex: revision.txt) or under a directory
(r1234/src) that your build can then use to determine the revision of
the code. If you're building from within a subversion workspace, then
you can get the current revision number by running 'svn info' on the
root of your build tree.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-03 16:54:00 CEST

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.