[p4dti-discussion] Building P4DTI

[Nick Barnes]

At 2005-12-19 14:45:08+0000, Stephen Vance writes:
> It seems that the build procedure for the P4DTI is designed 
> specifically for the Ravenbrook environment. This includes some 
> references in build.py that assumes a Perforce environment layed out 
> the right way as opposed to from the kit. The paths in the build 
> document need some interpretation to contextualize to the kit and 
> even that is only approximate.
> 
> Am I missing something? What is the build procedure from the kit?

You're right; the build script is intended for use at Ravenbrook to
build a new release from a complete project client, including (for
instance) the Bugzilla releases as trees in the appropriate spots in
the import/ directory (required for making the Bugzilla patch files).
I'm not sure what the exact dependencies are.  There is no written
procedure for building a release of the P4DTI from the kit.

I suspect the main problem building from a kit would be the absence of
Bugzilla release trees in appropriate places in an import/
subdirectory of a parent directory.  The kit includes the build script
itself and the build procedure documentation
(procedure/release-build/).

Nick B