RE: [Rainbowportal-devel] CVS cleanup

[Cemil A. <cem...@ya...>]

> My last comment is that I'm not sure, but isn't the CVSROOT folder supposed
> to be just a folder where cvs stores its stuff and you put your modules in
> root folders beside it, not in it?  This is the only project I've seen that
> puts stuff in there, that's why I'm asking.  :-)

I noticed that too.  CVSROOT is for cvs config files and should only be updated
by the CVS administrator.  The best setup I've seen is to create a single top
level directory at the same level as CVSROOT then put all of our modules under
that one.  Using this method we can checkout, branch, tag etc... all of the
source with a single command which is very convienient. 

This structure assumes that you want to branch and tag all of the source at
once.  If you want to have projects that you don't want to tag or branch
together then you create another root level directory in the cvs repository.

Example...

/CVSROOT/            <-- Administrator ONLY
/Rainbow/            <-- branching or tagging here recursively tags everthing
---/RainbowCore/         beneath this directory
---/RainbowECommerce/
---/CoreModules/
---/CoreComponents/
---/AddOnModules/
---/AddOnComponents/
---/AddOnSkins/
---/Miscellaneous/
/Foo                <-- since Foo isn't beneath Rainbow it isn't tagged or
                        branched

=====
Cemil Ayvaz