On Wed, 27 Oct 2004 15:38:36 +0200, SteveKing
<stefan.kueng@wagner-group.ch> wrote :
>Duncan Murdoch wrote:
>> Last year there was a discussion on this list about the problems of
>> implementing an svn:keywords subsitution keyword which puts in place
>> the global revision of a source tree. The general impression I got
>> from reading it was that this was too much of a special case need to
>> justify putting it in.
>
>You mean this:
>http://subversion.tigris.org/project_faq.html#version-value-in-source
>?
Yes, that's what I'd like to happen, but the instructions on that page
don't quite work for us. Some people do builds from source tarballs
or from svn export copies. We could use svnversion to put something
into the tarball and tell people using that not to use svnversion; we
could tell the people using svn export to use svnversion in their
builds, so there are definitely workarounds. We're just looking for
the simplest one.
The FAQ you pointed to says this:
>Subversion increments the revision number of the repository as a whole, so it can't expand any keyword to be that number - it would have to search and possibly modify every file in your working copy on every update and commit.
>
That's a problem with one implementation, but that's not the only
implementation. Another would be to store in some global location
(wherever the revision number is stored) a list of files containing
this keyword. Whenever the revision number is updated, those files
would be marked as changed too.
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 27 16:06:23 2004