Jay Yarbrough wrote:
> I'm quite new to using CVS.
>
> Our applications rely on common source, and built products alike.
>
> Some of these are 3rd party (dlls, jars, source, etc.) and some are internally
>developed.
>
> For instance, to build release 1.2 of product X, I need release 3.4 of product A,
>release 5.4 of product B, and release 1.1 of product C.
>
> To build release 2.1 of Product Y, I will use release 3.4 of product A, release 5.3
>of product B, and release 2.0 of product D.
>
>
> How is this typically handled within CVS?
It isn't. It's a configuration management problem, CVS is an
archiving system. Because configuration management and archiving are
so tightly linked in practice, people tend to miss the fact that
they're conceptually separate.
I am, unfortunately, not terribly familiar with available CM tools.
Many folk seem to be happy with simple homegrown CM models, and I see
a couple of suggestions have already been forwarded. I just wanted
you to be aware that whatever solution you pursue, you should be able
to use CVS to do the archiving.
/|/|ike
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
