Make a distinction between modules and subsystems. For this, I'll use SA to mean "subsystem A", SB to mean "subsystem B" and so on.
Create modules for each subsystem: subsystem-A src/A subsystem-B src/B subsystem-C src/C subsystem-D src/D Then create your modules to contain the proper subsystems: A -a subsystem-A B -a subsystem-A subsystem-B C -a subsystem-A subsystem-C D -a subsystem-A subsystem-B subsystem-C subsystem-D There are a number of variations of this to try, depending on the organization of your code, but this kind of factoring is the key to accomplishing what you want. --- Forwarded mail from [EMAIL PROTECTED] I've got the following modules with their respective compilation dependencies: A depends on nothing B depends on A C depends on A D depends on B and C How to organize such a structure under CVS? Indeed, if I set the dependencies the way it is mentioned above, I'll get A twice when I'll checkout D in my working dir. --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
