[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs commit as root

From: Greg A. Woods
Subject: Re: cvs commit as root
Date: Fri, 7 Dec 2001 21:56:54 -0500 (EST)

[ On Friday, December 7, 2001 at 11:13:14 (-0800), Harry Putnam wrote: ]
> Subject: Re: cvs commit as root
> This sounds like a very smooth way to have it setup.  However well
> above my level of understanding of the needed proceedures.  Definitely
> something to look into... thanks.

There's nothing really too magic -- unless you're trying to manage
several systems from one consistent set of "source" files....  But
that's what a more sophisticated management tool such as cfengine is

In the simplest case you could just blindly copy all the files from your
working directory (or exported release) and be done with it, which
really isn't much different than what you've been trying to do, except
that now you have to edit them in a working directory first.

Where this gets really interesting is if you have multiple people
managing your systems.  When I last did this kind of thing with CVS we
simply made a rule that everything had to be committed to CVS,
preferrably before you ran 'make' to install the files, but at least
very soon afterwards; and that you had to do a "cvs update" before you
tried to edit anything.  We had contemplated putting checks in our
makefile to help enforce these rules, but pretty well everyone had an
early experience with losing their changes because they got clobbered by
someone else running 'make' from another directory and they quickly got
into the habit of doing things more carefully.

                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]