In this case ignoring svn, cvs related files in a global manner if okay since those are not desired in the production cfengine area (at least I don't desire them). In general I do stay away from things like this except when ignoring source control related files like .svn, CVS, etc.
What types of problems might on encounter when ignoring .svn files in a global manner? Steve -----Original Message----- From: Brendan Strejcek [mailto:[EMAIL PROTECTED] Sent: Thursday, January 19, 2006 10:10 AM To: Nielsen, Steve Cc: Atom Powers; Bas van der Vlies; help-cfengine@gnu.org Subject: Re: [Cfengine] RCSs and CFEngine Nielsen, Steve wrote: > Neither. It stands on its own: > > ignore: > any:: > .svn > > This will cause any cfengine statement that deals with files to ignore > .svn directories (and their contents). <opinion> I think this is dangerous, particularly if you have more than one admin involved in your cfengine policy. Once your collection of input files grows past a certain size, these global declarations almost always start to interact with your configuration in unforeseen ways. I would recommend using ignore=.svn in the copy statement. It is easier to read, and will be safer in the long term. </opinion> Best, Brendan -- Senior System Administrator The University of Chicago Department of Computer Science http://www.cs.uchicago.edu/people/brendan http://praksys.blogspot.com/ _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
