[Top][All Lists]

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

Modelling project dependencies in CVS

From: Mario Philipps
Subject: Modelling project dependencies in CVS
Date: Sat, 28 Dec 2002 21:31:56 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826


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,


reply via email to

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