Dave Rolsky wrote:
To say it in my own words, this person does not want to "pre-install" Module::Build on the systems she (I think) is using to do CPAN testing. However, since CPANPLUS does ship its own (out of date?) version of Module::Build, things mostly work, because if a module only has a Build.PL, CPANPLUS will use its own version of M::B.
I don't think that is it; if you review my exchange, the OP seems to think that CPAN Testers should only use the O/S supplied Perl with base installed modules, i.e. *no* additional modules. This sort of 'extremely white box' testing is foolhardy at best (IMHO), since the very first thing *I* doing after installing a system (any system), is start installing my default toolchain - which begins with Bundle::CPANPLUS (fight through the few recalcitrant dependencies) and then installing anything else via the `cpanp` client. I often don't even upgrade CPAN to the latest version (no offense intended, Andreas).
I think she should just freaking install Module::Build on the testing machines. To say that this is now a prereq for doing testing is hardly a ridiculous statement, any more than suggesting that you should have a vaguely recent version of EU::MM.
I made the point at the end of my exchange that I consider Module::Build to be a dependency just as much as Test::More is a dependency. I knew you would probably agree with me on this point, but I'm looking for less emotionally involved answers too... ;-)
John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748
