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

Re: [PROPOSAL] Expansion keywords/properties enhancement

From: Matthieu Brouillard <matthieu.brouillard_at_agfa.com>
Date: Thu, 11 Sep 2008 09:32:49 -0700 (PDT)

David Weintraub wrote:
> 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.
I have no problem to put some replacement at build/deliver time for
replacements that are the same for each files; for example copyright is the
same for all the files and can be replace at build time.

But my need is that each file, once it is commited, gets a new version
(generated by some algorithm). We use this mechanism for database objects
and for auto-update mechanism on the client site.

As I said before, i am not blocked by not having such a feature.
I will install a double commit mechanism using hooks. My though was just
that if an expansion mechanism already exists in subversion, why not
extending it. The "only" need would be to be able to contribute to meta-data
with an external/plugin/contribution mechanism.

Thanks for your thoughts, I will put in place the double commit mechanism.

View this message in context: http://www.nabble.com/-PROPOSAL--Expansion-keywords-properties-enhancement-tp19408635p19439001.html
Sent from the Subversion Users mailing list archive at Nabble.com.
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 18:33:20 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.