RE: Possibly not possible

[Jimmy Rimmer]

It looks to me like what you REALLY want is a single repository, and several
branches/tags on the source tree, one for QA, one for Development, etc.

-------------------------------------------------------------------------
Jimmy Rimmer, address@hidden      http://mp3.com/Rimbo?edSig
-------------------------------------------------------------------------
"We admire our teamwork and skill, forgetting, as always, the stupid way
we got into the situation in the first place.  If you do lots of dumb
things, you get to be a hero."  --Daniel Hays, _My Old Man and the Sea_


> -----Original Message-----
> From: Emmanuel van der Meulen [mailto:address@hidden
> Sent: Thursday, October 04, 2001 12:13 PM
> To: address@hidden
> Subject: Possibly not possible
> 
> 
> Hello all,
> 
> This is my first time here.
> 
> I have attempted to do a certain configuration but was not 
> successful.  I might
> have a unique requirement - but I find it hard to believe 
> that I've come up with
> a requirement which CVS does not cater for.
> 
> I'd like someone to please a) confirm whether my scenario is 
> not catered for in
> CVS, or b) whether my implementation is incorrect and c) in 
> the event that this
> requirement is possible, to please assist me in setting CVS up for my
> requirement, and then d) where this is not possible but you 
> find this of use,
> could CVS please be extended to cater for this requirement - 
> then how would I go
> about requesting this as an extension to CVS.
> 
> I request please that you do not supply me with assistance if 
> you do not follow
> exactly what my requirement is - in which case rather ask and 
> I'll gladly
> elaborate.
> 
> 
> Here goes;
> 
> 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
> 
> 
> Usage of above;
> With above configuration, whenever source is COMMITted to 
> ProdSource, from
> either ReleaseSource or QASource, those changes could then be 
> used to UPDATE
> source in either ReleaseSource or QASource - enabling that 
> when changes are
> applies from ReleaseSource, those are also available to 
> QASource and visa versa.
> 
> This would make changes applied to 'service packs' available 
> to QA of next
> release and visa versa.  In addition any change made in QA 
> which applies to the
> previous release, is made available to further 'service 
> packs'.  These changes
> are in addition also made available to development of the 
> next release, seeing
> as DevSource gets source from QASource.
> 
> 
> Hope this is clear and thanking you in advance where someone 
> could assist me.
> 
> Kind regards
> Emmanuel
> 
> 
>