Is it possible to add files to subversion that isn’t supposed to be versioned? F.ex. config-files that needs to be edited to match each individual environment. When a new programmer is connected to the project he should get the original file from subversion but it wont be commited after he edits it and it wont be overwritten when he updates.
Maybe creating a tag for the whole original-project is the solution? First downloading the tag and then update from trunk?
Any ideas?
Clarification to comments below: The project (Sitecore) consists of about 30k number of different files. We need to version about 100 of these. If we should include all files in the versioning then each commit takes forever (as tortoise searches through all folders). Today we create a zip-file containing all the unversioned folders, sets the folders as ignore in svn and then add the zip instead. Problem is when we need to change one or more of the files in the zip, then we need to commit a new ~1GB-zip to the repo.
I’d put the unversioned files up on a web or file server accessible to everyone using the project, and add a script to automatically (
wget/scp/etc.) download the files (zipped if needed) and extract them to svnignored folders so that they don’t get picked up by subversion.If you are concerned about these files changing, then: shouldn’t they be versioned?
svn:externals may be useful in this situation too. I think they can be set up to be ignored easily as circumstances permit.