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

RE: Re: How to handle configuration/ini files in a sandbox

From: Bob Archer <bob.archer_at_amsi.com>
Date: Thu, 26 Feb 2009 13:43:27 -0500

> In short, it would be nice if there was a feature where one could
> files from commits, but allow them to be updated. That way, if a
> is added to a ini file, all ini files (at production) could be updated

> Maybe the above solution is already there?
> Is it?

What you could possibly do is use a .template file as suggested in the
FAQ and on those machines where you want to use exactly what is checked
in then create a post update script that renames the .template file to
the correct name.

Then your devs would not have the commit script and they would know they
need to manually update there .ini files when there are changes in the



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-26 19:44:17 CET

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.