ps <[EMAIL PROTECTED]> wrote:
> Reading the cvs documentation I can't get past the first few lines.
> Nowhere can I find the definition for "module". The docs freely start in
> referring to modules everywhere, but the term is never exactly defined.
Yeah, it's a little ill-defined. Loosely speaking, a module is any
part of the tree under $CVSROOT that can be checked out as a unit.
For example, immediately after you do your "cvs init" there is a
$CVSROOT/CVSROOT subdirectory with cvs administrative files,
and you can check it its contents like so:
cd some/place/clean
cvs checkout CVSROOT
In that sense, CVSROOT is a module. After you import a few trees,
every top-level directory under $CVSROOT is a module because you can
check it out by name.
In that same CVSROOT administrative sandbox, you will find a "modules"
file. You can edit that file to make other subtrees of your repository
accessible by name, like the top-level subtrees. An entry like this,
scripts-A projectA/lib/tools/subtools/scripts
makes a deep subdirectory available through
cvs checkout scripts-A
So there is a somewhat more precise definition: a module is anything
that has an entry in $CVSROOT/CVSROOT/modules .
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
