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

RE: Re: Making a copy that follows?

From: Reedick, Andrew <Andrew.Reedick_at_BellSouth.com>
Date: 2006-08-30 23:16:17 CEST

> -----Original Message-----
> From: Hadmut Danisch [mailto:hadmut@danisch.de]
> Sent: Wednesday, August 30, 2006 3:02 PM
> To: users@subversion.tigris.org
> Subject: Re: Making a copy that follows?
> I am currently dealing with several software configuration files
> grouped in directories for different machines. Some of the files must
> be the same for all machines, other files are different.
> Softlinks don't do the task, since
> - You need to check out all directories
> - The local software always removes the old files and writes a new one
> when doing any configuration changes. So any link would be replaced
> with a plain file.
> That thought of having hardlinks in the file system is not important.
> The important thing is to be able to checkout the same file at
> different paths in the SVN tree. Every checkout of a subtree should
> have an up-to-date copy of the same file. This would make sense for
> many uses, e.g. README, Makefile, COPYRIGHT files and things like
> that.
> Under CVS I could have this simply by putting soft- and hardlink
> in the CVS repository itself. But with the migration from CVS to SVN I
> ran into the problem that this does not work anymore.
How about Plan B?
        Let the build and/or deployment script build the correct tree at
build time.
        The generic files would reside in a global directory. The
build/deploy scripts copies the global dir into your build/package dir,
and overlays it with the files in a custom dir. cp -pr
../global/generic dist/.; cp -pr ./local/custom dist/.
        Or you could tokenize the custom files. The global dir contains
the files with tokens. The token values are in a properties file in the
local build and are applied at build/deploy time.


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA624

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 23:38:52 2006

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.