Re: File under versioncontrol with individual changes per developer

Daniel Albuschat wrote:
> Or perhaps you have other ideas how we could circumvent this.

I can only offer a workaround...

What I usually do with files like this is to have a *.sample. This file
*is* under VC. I also set svn:ignore to the * part.

A specific example:
build.properties.sample -- Contains the base values, with dummy passwords
build.properties -- A copy of sample, with actual values in it

This I use with Java and Ant. It works pretty well.

What I would propose is to have another file with the developer specific
line in it, only. That file would not be under VC. Put a sample file.
  Then, during your build, (or after updating), concatenate both files
together to the target filename.

For example:
build.properties.sample -- VC'd file
build.properties.dev -- developer-specific file
build.properties -- Automatically generated file

So, checkout and update would become
svn update && cat build.properties.sample build.properties.dev >>
build.properties

Hope that helps !
François

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 16 15:55:44 2004