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

File under versioncontrol with individual changes per developer

From: Daniel Albuschat <daniel_at_viming.de>
Date: 2004-07-16 10:28:49 CEST


   I have a small problem with svn. There's a file
in the repository that needs to be changed by every
developer in order for the IDE to work properly.
Every dev needs to change a database path variable
in this file, so he has access to the db from within
the IDE, what's very helpful. The variable will get
changed if the program starts anyways, so the info
is only valuable to the IDE.
Well, this file needs to be under version control,
though, since there are other parts that'll change.
But everytime any developer does a commit, he overwrites
the file in the repos with his `new' version, where only
this variable changed. This leads to a huge version list
for this file of course, which is not needed.
And, if a dev updates, he overwrites his database path. So he
has to change it again after each update. This, too, is
pretty annoying.

Is there a way to `ignore' this file when doing a svn commit,
but make it possible to explicitly commit it via
svn commit <file>?
This would be really helpful.

Or perhaps you have other ideas how we could circumvent this.

   Daniel Albuschat

eat(this); // delicious suicide
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 16 10:29:14 2004

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.