Re: cvs commit as root

[Harry Putnam]

address@hidden (Greg A. Woods) writes:

> 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.

Well, its not really true that it `isn't much different'.  The copying
step is really a major pain in the butt.  And represents aboutt 50% of
the work needed to keep something in cvs.  Removing that step cuts the
work roughly in half and probably considerably more.  Considering it
creates extra steps for many other proecess as well.

For example: Diffing the file curently in use against the latest cvs
controlled version requires a more complex command line.

Or `cvs update' but then one needs to copy over the cvs files to
overwrite the ones in use.  In every way that extra step doubles the
work. 

With my symlinking setup, at least 50% and really more, of the
headache of keeping things in cvs is eliminated.  The more so since
one group of files (a small selection to be sure) is kept in a `misc'
module and is the source for 3 home machines.

Most config files do not lend themselves to this kind of thing so most
of the files I keep there are scripts that work in common on all OS
involved. (FreeBSD solaris linux)

Other than `misc', each machine is represented in skeletal form inside
CVSROOT by a module bearing the machine name (short version) and the
subdirectories that are usefull under it.

So a `cvs co' of the main module contains all machine mirrors.  (Each is
only a partial mirror, very small by comparison to a full OS)

All the machines have simlinks to a checked out module on board, that
remains in place.