I think this is a general Subversion issue, and not something Versions alone can address.
One thing folks I know often do is store a generic template file in the repository, then add an svn:ignore property to ignore versions with local modifications. For example, if you have foo.conf, you could version foo.template.conf with the understanding that users must duplicate this as foo.conf (and customize as necessary) after checkout. You could integrate some sort of script to handle that for you, which would be useful if there are multiple configuration files. Googling (especially on Stack Overflow) should turn up some helpful links. For example: http://stackoverflow.com/questions/577176/adding-unversioned-files-to-subversion http://stackoverflow.com/questions/1495796/subversion-management-of-project-configuration-files http://stackoverflow.com/questions/3366708/how-to-remove-file-from-subversion-make-it-unversioned Personally, I prefer to keep the file extension the same (rather than appending .template) because then it maps to the same application. For me, .template files try to open in Pages, which is incredibly annoying. :-P - Quinn On Jan 3, 2012, at 2:38 AM, Dan wrote: > Hi again, > My trial has now expired and I'd happily click 'Buy' if this question > were answered :) > > Dan. > > On Nov 30 2011, 4:06 pm, Dan <d.j.mcgr...@gmail.com> wrote: >> Hi! >> >> I'm trialing Versions because I'd like to solve a problem we have with >> our current repository setup. All our coders use different development >> environments which necessarily changes some configuration and other >> generated files. However, we need to store a basic version of these >> files in the repository so that new developers can jump into >> development straight away without spending hours and hours setting up >> the required configuration. This leads to having lots of files in our >> repositories which have local modifications but that we want to ignore >> when we commit. >> >> Does anyone have a solution (either in general or specific to >> Versions) such that we can ignore these files upon edit but whereby a >> version of the file can still sit on the server? >> >> One way would be for Versions to ignore locked files when a commit is >> attempted on them or their parents, would this be possible? >> >> Dan.
smime.p7s
Description: S/MIME cryptographic signature
