[ On Thursday, October 24, 2002 at 11:48:26 (+0200), Hauke Fath wrote: ]
> Subject: RE: using cvs to contol system files
>
> Am 23.10.2002 um 19:05 Uhr -0400 schrub Greg A. Woods:
> > > RCS is simple to use and gives you version control with few commands to
> >> know.
> >
> >I concur 100%
> >
> >I have in the past devised procedures and processes to use CVS to manage
> >system configurations (which ended up having to be much more complex
> >than vi1pdqyo02 was proposing), but I would not do so ever again without
> >using something like GNU Cfengine to do the work and then just use CVS
> >to manage the cfengine inputs.
>
> I use cvs for some system files/scripts that I use on several
> machines, but not with the target directory (/etc, /usr/local/sbin or
> whatever) as a sandbox. Instead, I add a Makefile so that a 'make
> install' places the file(s) with permissions set up properly.
>
> The files carry a dire warning in the head that any local changes
> will be wiped out with the next update.
Yes, that's what I meant by "procedures and processes" :-)
It's a major nightmare to re-invent something that ends up being very
much like cfengine without initially planning to go that far though.
--
Greg A. Woods
+1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
