[p4] Multiple Dependent Products in Perforce
dweatbrook at expedia.com
Wed Jul 26 19:23:40 PDT 2006
Check out ivy from jayasoft.org. You will likely see many ways that you
may use it to address what you are trying to accomplish.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
Sent: Friday, July 21, 2006 10:57 AM
To: Scott Goldstein
Cc: perforce-user at perforce.com
Subject: Re: [p4] Multiple Dependent Products in Perforce
There is discussion of this in Laura Wingerd's book Practical Perforce.
I also dealt with a number of supporting branching issues in my paper
from the Perforce User Conference 98 linked off my web site at
Scott Goldstein wrote:
> We'll soon be moving to a model in which we have multiple products
> their own lifecycle which have dependencies. For example, we'll have
> platform product and several application products which depend on
> artifacts from the platform, but each will have their own release
> We're thinking that we'll need some sort of repository for build
> artifacts from the platform and some way of declaring which version of
> the platform our applications will require and which build artifacts
> from the platform they'll require.
> Can anyone point me to examples or a best practices document for how
> my set up a source control and build environment for this situation?
> perforce-user mailing list - perforce-user at perforce.com
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user