[ERROR] [Fri Aug 15 07:46:43 2008] This module requires 'Module::Build' and 'CPANPLUS::Dist::Build' to be installed, but you don't have it! Will fall back to 'CPANPLUS::Dist::MM', but might not be able to install!
FAIL Test-Kwalitee-1.01 i386-netbsd-thread-multi-64int 3.1
I didn't choose my distro's requirements randomly. I chose them because they're necessary to build, test, and install my distro. I'm not sure what this failure report should tell me. It won't work without the requirements I've already indicated are requirements?
Someone should write a CPAN testers client in a language other than Perl so people can use it to report that CPAN distributions tend to fail on boxes without Perl installed.
I didn't choose my distro's requirements randomly.
I don't see anything there about build_requires or configure_requires, so I guess the smoke tool must be inferring this requirement (which it then ignores.)
While it is true that this sort of failure is representative of the box on which perl 5.6.2 has been freshly installed, I still question the utility of that (and the popularity of this smoke configuration.)
I would laugh about the "No Makefile.PL found, attempting to imagine one..." message, but I've heard that joke before too.
Re:This error message comes from the tester client
chromatic on 2008-08-15T23:26:33
Is there a way to mark build_requires or configure_requires with a stable and released version of Module::Build? If so, I'll use it (although I still foresee a batch of test failure reports from people running ancient versions of CPAN.pm and CPANPLUS.pm under the argument that "People who don't update Perl or their installed distributions really want to run the latest versions of distributions from the CPAN.").
Re:This error message comes from the tester client
Alias on 2008-08-16T22:22:17
If you release more than once a quarter and don't need to compile anything, Module::Install welcomes you with open arms.
Re:This error message comes from the tester client
chromatic on 2008-08-17T05:09:57
I still think that the Module::Install approach is very wrong, though -- and I'd like to see Module::Build release more than once every 16 months as well.
