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

Re: Feature request: Keyword $Rev$ with a twist

From: William Uther <will+_at_cs.cmu.edu>
Date: 2002-07-31 18:22:02 CEST

On 31/7/02 11:44 AM, "Mats Nilsson" <mats.nilsson@xware.se> wrote:

> Dave Cridland [mailto:dave@cridland.net] writes:
>> svn info gives you the last changed revision, as well as the current
>> revision, for any node.
>> AFAICT, for a directory, the last changed revision is when anything
>> inside it changed. I use these as build-revisions, and it seems to work
>> very nicely.
> Yes - but that still requires the build process to interact with the source
> code control tools. One more step to perform. I'd like very much to be able
> to separate these actions.
> I'd hate if it required me to write something like this in each Makefile:
> version.h:
> svn info . | grep Revision | awk '{ print "#define REVISION" $2 }' >
> version.h
> Not to mention all the troubles to remember to keep version.h updated after
> each 'svn up' (rm version.h; make version.h).
> And not to mention the troubles of doing this portably (MSVC vs. Makefile
> etc.)
> I'd like to do a simple 'svn up' and be done with it.

If I remember correctly, this has come up before. The issue is svn supports
mixed revision working copies (again, IIRC). You cannot guarantee that the
value in any file is up to date for any other file in the working copy. If
you add this keyword in the file revision.h, and then 'svn up' a dir that
doesn't contain revision.h, then revision.h will not be updated and will be
contain incorrect information.

I have no strong feelings either way. I just wanted to point out that this
has been discussed before. You might want to look in the archives for more

\x/ill :-}

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 31 18:23:11 2002

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

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