[p4dti-discussion] Building P4DTI

[Stephen Vance]

Sorry. The Bugzilla-specific comment was more about the wording in 
the job rather than a concern about build.py. My only concern about 
build.py is the assumption of a Perforce server in it, although the 
impact of that is not clear to me at this time.

Is the version log referenced in the build instructions the change 
log at the bottom of the readme? I was looking for something more 
immediate and direct. My oversight.

The version and release index are the kind of thing I was looking 
for. Why couldn't they be included in the distro? However, even a URL 
reference to them in the docs might help identify the next release.

Thanks for the attention.

Steve

At 11:09 AM 12/20/2005, Nick Barnes wrote:
>At 2005-12-20 13:54:38+0000, "steve at vance.com" writes:
>
> > I would like to make a suggestion that the tools provide a framework for
> > building other integrations and not just be Bugzilla-specific.
>
>If you mean tool/build.py, then they do.  Section 5.3 is the only
>Bugzilla-specific part of that script.  Section 5.2 used to build the
>TeamTrack integration, and was removed when that integration was
>dropped.  Adding another integration would be a case of writing the
>necessary section 5.x.  The details of what that section has to do
>would depend on the integration (the TeamTrack integration section
>used to run VC++ to build a TeamTrack module dll, for instance); it's
>not clear how much can be abstracted.
>
> > I would also like to see the documentation address the underlying
> > assumptions of knowledge of the Ravenbrook environment in order to
> > make it more accessible to the open source integrator. For example:
> > I spent some time trying to find the "version" directory under which
> > the release version root should be located; The readme.txt that is
> > supposed to contain the version history is not part of the kit, as
> > it resides in this directory; the documentation does not make the
> > format of the VERSION directory clear enough that it's obvious that
> > it might correspond to the p4dti-kit-2.3.0 directory.
>
>Hmm?  The readme.txt is simply at the top level of the version
>sources, and ships with the kit (as p4dti-kit-2.3.0/readme.txt).  As
>you can see from the build script (the build_kit function), the kit
>contains all of the versioned sources (including code, test suite,
>manuals, procedures, tools, etc).
>
>Possibly you mean the version index and release index
><http://www.ravenbrook.com/project/p4dti/version/> and
><http://www.ravenbrook.com/project/p4dti/release/>.  It's not clear
>whether or how these could be separated from Ravenbrook.
>
>I absolutely agree that there is scope for a "building a release from
>the integration kit" procedure (or sub-procedure), and for improving
>tool/build.py to support such a procedure.  I will look into this in
>more detail when I address job001292.
>
>Nick B

Stephen Vance
mailto:steve at vance.com
http://www.vance.com/