I've been following this conversation for a while, but I personally
haven't found much use for keyword expansion because almost all of the
information I need is actually available inside Subversion. In fact,
most version control systems no longer to even bother with keyword
expansion.
I also like the fact that Subversion is smart enough not to store the
expanded keywords in the repository. Otherwise, you'll have problems
with diffs and merges finding conflicts where none exist.
I am not sure what you would like to do, but it appears you want this
information available once the program leaves the confines of a
Subversion working directory and repository and is placed on a
customer site. That way, version information is readily available when
the client has some sort of problem.
A better mechanism is to design something yourself at package or build
time. For example, it isn't uncommon to have some sort of parameter
(like "@VERSION@") sitting in a particular file, and have this
parameter replaced by the build number some sort of version ID, or the
Subversion repository number when an actual build or packaging takes
place. In fact, there is the "svnversion" command that is used
specifically for this purpose.
You can easily do this for "copyright" and probably have it calculated
at package/build time, so no one really has to maintain it.
---------------------------------------------------------------------
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-11 17:50:37 CEST