Hierarchical team integration in CVS

[Earl Williams]

Hello all,

I'm hoping someone can help me with a seemingly basic CVS question that I've
not been able to figure out after extensive web research. In a nutshell, how
do hierarchically related teams structure their code into a repository's
modules?

For example, the following packages contain the source code for app Foo,
written by company Whee:

source.com.whee.foo                        (contains the project's main
class, Foo.java)
source.com.whee.foo.internals
source.com.whee.foo.toplevelgui
source.com.whee.foo.utilities
source.com.whee.utilities

Team A is responsible only for the internals package, and has written a
harness project to help them test their classes in isolation.  Team B is
responsible for all other classes in the app, and has written stub classes
to stand in for Team A's work.  Both teams use the classes in the two
utilities packages.

How should these teams use CVS?  A single module called "source" seems to be
the approach in the CVS documentation I've read.  However, this approach
seems not to accommodate the desire of Team A to to keep their stubs in the
"internals" package.  Also, Team B doesn't want to checkout the whole module
because then they would get lots of classes they don't care about (like the
toplevelgui classes); so does this mean they have to do a separate update
operation from three different folders in their local sandbox
(source.com.wheee.foo.toplevelgui, source.com.wheee.foo.utilities,
source.com.wheee.utilities)?  Or should the project use multiple modules, so
both Teams A and B would have to do multiple update operations from
different folders?

Surely I'm unclear on something basic here.  Thanks very much for any help.

-Earl Williams