Test::SDK currently has too many unresolved problems, so I'm pulling it off CPAN until they're solved.
There's two major problems stemming from one cause. First, there's no safeguard against an older version of the module in the SDK blowing over a newer installed version. This will happen if the version in the SDK falls behind the independently distributed version, as tends to happen. Second, there's no way to install parts into the perl core directory and parts into site_perl. In this case, Test::Harness has to go into the core lib directory, everything else into site_perl. This all stems from the simple "dump everything into one big blib/ and let recursive make do the rest" approach. Something a little more sophisticated will have to be found. I suspect what it will be is pretty much what CPAN does: Have the SDK's top level Makefile.PL calculate the module dependencies by running each underlying Makefile.PL and looking at the resulting PREREQ_PM. It then orders them in terms of which needs to be installed first. In Test::SDK it would be Test::Harness, Test::Simple and finally Test::Inline. Then each module is individually tested and installed in turn. Before performing the test & installation it first checks that there's not already a higher version installed. If any one fails the sequence stops. This shouldn't be too much extra work to pull off. The only unknown I'm pondering is if it's worth trying to wedge this into the usual "perl Makefile.PL; make; make test; make install" sequence or to just have a simple "installsdk" program that gets run. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One Monkey tennis
