I want to use subversion to manage config files in a cluster. The
servers were historically maintained by hand so the configs have drifted
apart. The goal is to eventually have a single identical config on all
the servers but for practical reasons this won't happen overnight.
My plan is to have a trunk for the "ideal" config. Each server will
initially be imported into a branch using the in-place-import technique:
http://subversion.tigris.org/project_faq.html#in-place-import
I'll then use svndiff and svnmerge until the branch equals the trunk, at
which point I'll use svnswitch. Then the server will be managed under
the trunk. Everything sound good so far?
My problem is that some configs need specific UNIX ownerships and
permissions. For example, 0600 is needed by several config files.
Subversion naturally doesn't preserve platform specific information like
that.
Has anybody written anything that ties into the svn:props and/or
repository hooks that does what I want? I really want to avoid
additional steps after checkout (eg, fixperms.sh or something equally
cumbersome).
Notice:
The information contained in this e-mail message and any attached files may
be confidential information, and may also be the subject of legal
professional privilege. If you are not the intended recipient any use,
disclosure or copying of this e-mail is unauthorised. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete all copies of this transmission together with any attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 13 05:40:37 2004