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

Enhancement suggestion

From: Brad O'Hearne <brado_at_neurofire.com>
Date: 2005-03-03 00:08:39 CET

I don't know if this is the proper place to post an enhancement request,
but I was thinking that an interesting feature would be the ability to
have files flagged to be handled with context-sensitive versioning. In
other words, 99% of the content of my projects contains code that's
global, for any user that uses the project. However, there are
configuration files, either for users or for deployment situations that
I would like to be slightly different based on the context they are used
in. It would be really cool to be able to have these configuration files
overloaded within a revision number, by some uniquely identifying
context. So for example, if a project is at revision 10, and within my
codebase I have a brad.conf file, which is slightly different depending
on whether I am building for development or production environments, I
could do something like the following:

svn checkout -r 10 -context "dev"


svn checkout -r 10 -context "prod"

and I would get the exact revision, with variances in brad.conf for dev
and prod. The thing about files like brad.conf and similar config files
this is that neither one (the dev or prod version) is really a
progressive revision of the other, so to just commit changes is going to
be perpetually redundant, and required whenever a deploy is done.
Additionally, it doesn't fit the use case for a branch very well. It
also mushrooms admin if you store multiple copies of these things --
this is merely a small example, but it would require changing associated
builds to pull files from different places and other types of overhead
just to work with multiple copies of the file within a revision that
reside in different places, the location denoting the context.

So having the ability to have multiple contexts for a file within the
same revision seems useful. Thoughts?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 3 00:10:59 2005

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.