RE: cfengine and revision control

[Luke Youngblood]

Are you talking about this?

http://www.contactor.se/~dast/svnusers/archive-2003-08/0255.shtml

I looked at using the asvn script to check in all of /etc to an svn
repository, but found that it couldn't handle named pipes properly (there
are several in /etc on Solaris).  Good luck.

-----Original Message-----
From: Josh Lothian [mailto:lothian+cfengine@cs.utk.edu] 
Sent: Tuesday, May 10, 2005 8:54 AM
To: Luke Youngblood
Cc: help-cfengine@gnu.org
Subject: Re: cfengine and revision control

That was my original thought as well, however there's that period of time
between the end of the copy pass and before the files pass completes
that some files may have unknown/wrong permissions.  Some of our users
are rather vocal when things break, even for a short period of time.

Right now I think my two best options are:

1. using the aforementioned wrapper around subversion to set the correct
file permissions on the master by calling some script.

2. Setting properties on each file that specify what the permissions
should be, then using some hooks which reset the file permissions when
an update/checkout is performed.  In which case, this becomes purely a
subversion issue and not a cfengine issue.

The idea from the SingleCopy Nirvana discussion on the wiki is
interesting, but one things it adds it a couple more steps of complexity,
which I'm not a big fan of.  There may end up being 5-10 other people
mucking with the configs, and the less I have to explain/maintain the
better :)

-jkl