Modelling project dependencies in CVS

[Mario Philipps]

Hi,

i have three projects A, B and C, that are all under current development. Project A is some kind of a library, and projects B and C depend on it. Now i see only two solutions to this, but both of them seem to be really nasty:

1. Project A exists three times in the repository, once as a module (since it is under development itself), and once as subdir of projects B and C each. But this would cause big trouble to keep these three versions consistent and up to date.

2. Project A only exists as its own module, and projects B/C refer to A in the kind of ../projectA/, which means they contain paths leading outside the working copy. This would force everyone who wants to work on projects B/C to checkout A as "projectA" in the same folder.

I think there must be something better, but I don't see it ...


Thanks in advance,

Mario



_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs