On Tue, May 27, 2008 at 5:52 AM, Barbie <[EMAIL PROTECTED]> wrote: >> That's only a failing of CPANPLUS/CPAN::YACSmoke. >> CPAN::Reporter::Smoker requires Module::Build because I think a smoke >> test should assume a relatively modern toolchain. In my opinion, >> smoke testing "bare metal" installs of years-old Perl doesn't add a >> lot of value. > > Sorry David, but I have to take exception to that. It is not a failing > of the YACSmoke toolchain, as we try and keep prerequisites to a minimum > on purpose. > > Forcing testers to upgrade to the latest and greatest of everything is > not going to give the tester/author an understanding of what the 'user' > is going to experience when they install a distribution.
I have to take exception to the exception. Automated smoke testing is not the same as a installation by a user that has human awareness and judgement. (Though perhaps I give too much credit to users.) Moreover, from my perspective, a distro that needs Module::Build has a prerequisite and we've said that prerequisite failures should be discarded, not submitted as FAIL. So if we can identify the prerequisite condition, we should discard, not submit FAIL. >From what I have seen CPANPLUS/CPAN::YACSmoke doesn't do that. So I propose that it should either require Module::Build or else detect the failures and discard the reports. David
