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

> In short, it would be nice if there was a feature where one could
exclude
> files from commits, but allow them to be updated. That way, if a
parameter
> 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
.template.

BOb

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1234252

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