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

How to overlay files?

From: Langjahr, Uwe <uwe.langjahr_at_hp.com>
Date: 2005-10-05 08:07:21 CEST

A newbie question or not? I'm a newbie ;-)

Assuming you have three systems (development(D), testing(T), production(P))

for a small scripting environment. A simple script "a.pl" reads a

config file "a.cfg", which contains environment specific informations

(e.g. db connect, hostnames)

I'm looking for ideas, how to organize the SVN repository project

structure to handle the following situation or how I have to work

with SVN itself.


The script a.pl is modified in D, and should be transported to T for testing

(executing "svn update" in T for the whole directory/project).

But the config file "a.cfg" should not be overwritten.

Additionally "a.cfg" must be also under version control in

all three environments.

I found a way how I can do this:

- Instanciate the following environments (T, P) from the master (D)

- Only branch the config file "a.cfg" in (T, P) specific folders

- "switch" to the branch only for config file "a.cfg" to the specific

working copy in the specific environment

- The rest of the files ("a.pl") is derived from D.


Is this the best way, how I can handle this problem?

I think, this is a typical problem for all developers, who

have to support this three stages.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 5 08:09:11 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.