On Tue, May 27, 2008 at 12:04 PM, Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote: > a prereq. There is no way you can teach this audience how to > diagnose installation failures, and that's as it should be since > they have absolutely zero need to know anything about the CPAN > ecosystem.
You can teach this audience to install Bundle::CPAN. The "purist" case used to justify "bare bones" testing is fundamentally flawed anyway: E.g. CPAN::YACSmoke doesn't require Module::Build so as to minimize dependencies and show what a 'real user' might see as an error. Except that a real user of bare-bones Perl prior to 5.10 wouldn't have CPANPLUS in the first place and would see a completely different form of failure. So it's an artificial case to begin with. If you can tell people to install CPANPLUS (or CPAN.pm) you can just as easily tell them to install Bundle::CPANPLUS or Bundle::CPAN and get the toolchain upgrades anyway. And I would suggest that anyone you think should need to know nothing about the CPAN ecosystem shouldn't be installing modules via CPAN or CPANPLUS anyway, but should be using a packaged perl that can provide more robust dependency resolution via ppm, rpm, deb or whatever anyway. -- David
