common vs confidential development parts

[Xavier Marichal]

Hi,

anybody ever tried the following? Or any hints about it?

We need to team to collaborate around the same basis but to develop
separate (and confidential) add-ons.

So, in the src/ directory we have stuff like
A-module1
A-module2
A-module3
...
B-module1
B-module2
B-module3
...
C-module1
C-module2
...

The constraints are
A modules should only be accessible to team A
B modules should only be accessible to team B
C modules should be accessible to all

But how can we avoid the hassle of having to cvs-handle every module 
individually...
What would in particular be very annoying for releases...

Thanks for any help,
Xavier