[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

How to handle 'read only' files?

From: Markus Karg <markus.karg_at_quipsy.de>
Date: 2005-10-12 09:11:43 CEST

Hello Subversion Community,
today I have an organizational question.
We are using ANT for building our projects, but to make it work on each developer's machine we need some local settings. So we wrote an additional 'local.properties' file that gives build.xml the needed local information (like local paths etc.). It's clear that we cannot put that file on SVN since everybody needs different content in it, so everyone has his own local copy. But now new team members complain about the need of an 'initial' copy of that file: The don't want to write their own copy from scratch, but want to have a template. Until today, we did this by copying the local.properties file from one machine to the next, changing the entries where needed.
Sure this works well, but maybe there is a smarter solution using SVN? It would be great if we could just add the local.properties file to the shared repository, but tagging it as 'Read Only'. That shall result in the following behaviour:
- Each local change shall not be put back into the repository.
But there are two questions with that:
(a) How to do that? Can we just add it to the repository and then add it to the ignore list?
(b) How to modify that template if needed? Since local modifications don't get committed then, I can't change the template.
Any ideas are very welcome! :-)
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D
Received on Wed Oct 12 09:14:05 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.