Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Adding unversioned files to subversion

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.

like image 491
Zooking Avatar asked Feb 23 '09 10:02

Zooking


People also ask

How do I add a folder to svn repository?

Right Click the new repo and choose SVN Repo Browser. Right click 'trunk' Choose ADD Folder... and point to your folder structure of your project in development. Click OK and SVN will ADD your folder structure in.

How do I commit all modified files in svn?

If your working copy is up to date and there are no conflicts, you are ready to commit your changes. Select any file and/or folders you want to commit, then TortoiseSVN → Commit.... The commit dialog will show you every changed file, including added, deleted and unversioned files.

What are Unversioned files?

"Unversioned content" or "unversioned files" are files stored in a Fossil repository without history. Only the newest version of each unversioned file is retained. Though history is omitted, unversioned content is synced between repositories.


1 Answers

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.

like image 163
David Dean Avatar answered Oct 05 '22 08:10

David Dean