At 10:15 AM 9/26/2002, Jay Yarbrough wrote: >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?
Make each product a separate module. Then you can tag each release of each product and export them independently. Here's a way to build your product Y: Keep each released version of every product in some well-known place. This goes for third party products as well as your internal products. For example, build release 3.4 of product A and put it in /company/product/V3_4/A.zip or something like that. To create a release of product Y, your build procedure can use the released versions of the products it depends on. There doesn't have to be a distinction here between your internal products and third party products because they are all referenced in a similar manner. Fred _______________________________________________________________ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
