Question

I am working on a large web project which is managed in an SVN repository.

Each time a team member checks out the project, or we check out the project on a new production server, we have to modify a custom configuration file for that server. I have a “config.ini.base” file under revision control, which we keep updated with the latest settings, the idea being that team members copy that to create their “config.ini” (which is listed under ‘ignore’ on the directory).

To avoid confusion and mistakes, I’d like to somehow block any changes to “config.ini.base” from being committed to the repository, unless it is committed explicitly or the read-only setting is somehow explicitly overridden. How would I do this?

Answer 1

svn lock

Also, worth a read is Advanced Locking