On Sun, 1 Oct 2006, Adam Kennedy wrote:
The "right" solution is the same one as mentioned before... that the codebases of CPAN and Module::Build shouldn't be bleading into each other, that the CPAN client and the module installer should remain seperate and communicate by some sort of other mechanism.
Well, I still think that Module::Build->current() could do a better job of finding the appropriate build class, regardless of what CPAN.pm uses.
-dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
