My problem is this:
We have subversionized our PHP webapp projects, but each installation,
each checkout, requires different config files (to specify your
database, username, password, etc). We would like our project to have
default files with comments, basically vanilla config files. However,
with multiple developers working on a project, each with their own
checkouts and database information, that means that that
version-controlled config file wants to be checked once the checkout is
customized to that user and thereafter.
Is there some way to svn ignore that file, so that, although it is under
version control, it won't be checked in after you tell it to ignore that
file? (I don't want to remove the file from version control because the
vanilla version should be in there)
Is there some way to specify at the repository level, "Hey, this file is
read only!! Only check out versions of this file, don't commit unless
explicitly told to." ?
Is there some nifty trick on how to use subversion or good
packaging/project practice to achieve this desired behavior?
Thanks,
Erich Enke
Ruffdogs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 2 17:01:11 2004