Re: Exclude Files from commit

Robert Krugmann wrote:

>[...]
>A configuration file resides in our repository and shall be kept there. For
>certain reasons users want to make local changes to such a file
>and do NOT want to commit it (accidently) into the repository.
>[...]
>
>

This is a problem I ran into before, with files that are manually
changed as well as with files modified by the build process. The
cleanest solution is to checkin a differently named template to the
repository and have the developers or build process copy / modify it
over to the real name.

Like GNU autoconf configure.in -> configure

Eclipse users see that with .project and .classpath too, when they like
to keep local sources of libraries for debugging.

What would be really neat would be a client-side checkout (script? /
function?) that could copy the template to the real name if it is
missing, and leave it be if it exists. May issue a message or warning if
the versioned template changed. Extra bells and whistles points for a
merge operation.

Smells like a svn:<property> thing.
For instance: .classpath.in with property svn:template-for = .classpath

Any takers?

/Klaus

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 15 13:19:08 2004