[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possibly not possible
From: |
Matt Riechers |
Subject: |
Re: Possibly not possible |
Date: |
Thu, 04 Oct 2001 16:25:48 -0400 |
Emmanuel van der Meulen wrote:
>
> Overview;
> I want to make use of several repositories (at second level of structure)
> intercommunicating with each other via a root (at top of structure), with
> working directories (third level of structure) feeding off their repositories
> (at second level), thereby keeping different versions of source separate but
> enabling updating across separate 'routes' of development.
>
> Detail of CVS repository and working directories;
> 1).
> ProdSource - CVS root
> ReleaseSource - CVS working directory with ProdSource as CVSROOT
>
> 2).
> QASource - CVS root as well as CVS working directory with ProdSource as
> CVSROOT
> QAWorkSource - CVS working directory with QASource as CVSROOT
>
> 3).
> DevSource - CVS root as well as CVS working directory with QASource as CVSROOT
> DevWorkSource - CVS working directory with QASource as CVSROOT
If you just want to include modules in other modules, use the modules file
<http://www.cvshome.org/docs/manual/cvs_18.html#SEC155>. I assume you want 3
working directories that look like:
1. ProdSource/
2. QASource/
qa_sourse/
ProdSource/
3. DevSource/
dev_source/
QASource/
qa_source/
ProdSource/
The DevSource module would include dev_source and reference QASource, which in
turn would include qa_source and reference ProdSource. What limitation in the
module mechanism do you see that doesn't support this model? Am I missing
something?
-Matt