On Sep 12, 2006, at 8:20 PM, Adam Kennedy wrote:
Frankly, I think anything you might write to try and pick and
choose what to install is going to have problems.
Since we're wasting... ermm... using all this extra disk space for
tests anyway, why not just do the lot.
Take the entire distribution post-make and just tarball that up and
save it somewhere.
Then if needed, you can unroll it later, rerun the tests with
including blib, and there you go.
It's a little on the brute force side, but it should work.
Adam K
I agree with all this except the post-make idea. The "perl
Makefile.PL/Build.PL" step often does runtime things, like check the
version of Module::Build or insert boilerplate into Makefile. If
your install tools are updated between initial install and later re-
test, this could go haywire. Except for processor time, I assert
that you're better off starting with a clean tarball as if it's a
fresh install.
The only reason I can think of for the post-make argument is to
preserve choices made during Makefile.PL, like Module::Install
optional prereqs.
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
Clotho Advanced Media, Inc. - Creators of MediaLandscape Software
(http://www.media-landscape.com/) and partners in the revolutionary
Croquet project (http://www.opencroquet.org/)
