>>>>> On Sat, 30 Sep 2006 23:38:57 -0500 (CDT), Dave Rolsky <[EMAIL PROTECTED]> >>>>> said:
> 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. Besides that I think that CPAN and Module::Build are NOT bleading into each other here. It seems a very clear separation to me when CPAN just asks my $requires = Module::Build->current->requires(); my $brequires = Module::Build->current->build_requires(); and because of that I do believe that it is easy to decide who owns the bugreport. -- andreas