Reputation: 11778
I'm always having this problem and I didn't found the answer yet really.
Let's say you setup your partner setups a new project and imports every single file of the it, including those ones related to enviroment configuration which should not be under source control during the development (ie. the database config file).
So then I checkout the project for the first time and obviously I have to change the database config file to make it work. But then that file is marked as changed and will be show under the commit list, so is there a way to "unversion-it" at that point?
I tried "Delete and add to ignore list", but that will just mark the file to be deleted and once I commit, my partner will update the project and found that his db config file was deleted.
So how is really the way to work with those environment-dependent files? (Supposing you've already add them to the repo). You just change the file locally and keep unchecking it on every commit?
Thanks, and sorry if this is a silly question.
Upvotes: 3
Views: 463
Reputation: 11841
It's a pain in the backside, but there's always this. I've not use subversion much until recently, so I hope there's a better solution. It does give me what you want, though.
Upvotes: 0
Reputation: 15154
Tell your partner to backup the file and then use the Delete option from the context menu. It will be then also deleted in your copy and will not be versioned anymore.
Upvotes: 1
Reputation: 39869
I think many applications have a db.conf.sample
that they put in version control, and then people rename it to db.conf
which is ignored on the version control.
Upvotes: 7