[Top][All Lists]

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

RE: Nesting projects

From: Teala Spitzbarth
Subject: RE: Nesting projects
Date: Mon, 1 Jul 2002 20:02:24 -0700

What I have found frustrating with subdirectories being their own module, is 
that subsequent 'update' commands pull in the other directories - at least if 
you use aliased modules...    

I.e. [b  -a a/b,  c -a a/c] one does a "cvs co b"; then in their working 
directory at the a level later do an update, all other 'submodules' (i.e. "c") 
will be freshly brought over into the working tree...

I am still using CVS1.10.7 server (unfortunately) - so perhaps this has 
been addressed - or I guess it may just be a limitation of using aliased 


-----Original Message-----
From: Larry Jones [mailto:address@hidden
Sent: Friday, June 28, 2002 7:32 AM
To: Rich Bodo
Cc: address@hidden
Subject: Re: Nesting projects

Rich Bodo writes:
>       If I have a repository with projects A, B, C, and D.  And I
>       want to make B and C subprojects of A.  When I checkout A, I
>       also get it's subprojects B and C.  But when I check out B, I
>       get only B, and B gets treated like a it's own module by cvs,
>       and makes me feel warm all over when I see it all listed as if
>       it were a directory tree in viewcvs.
>       Is this what rtag is for?

No, that's what the CVSROOT/modules file is for.  The most natural thing
to do in your scenario is to make B and C subdirectories of A but give
them their own entries in the modules file.  Something like:

        a       a
        b       a/b
        c       a/c

-Larry Jones

Monopoly is more fun when you make your own Chance cards. -- Calvin

Info-cvs mailing list

reply via email to

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