On Tuesday 11 December 2007 4:27 pm, Michael G Schwern wrote: > FWIW I talked with Jos about it and I'm working up a patch to make CPANPLUS > Do The Right Thing, which is to install Module::Build as an implied prereq. > > > PS. You may want to add "configure_requires => 'Module::Build' " as > > well. But most CPANPLUS-based toolchain does not honor yet (or so I > > think). > > I worked with Jos and submitted a patch for that. > http://rt.cpan.org/Public/Bug/Display.html?id=29676 > > Still needs a little work, like tests and docs and stuff, but it looks like > the CPANPLUS vs Module::Build fight will be over soon.
Thank you. :) I'll be so happy when I don't have to jump through hoops to get things to fail gracefully when CPANPLUS already knows that it doesn't have everything it needs to do a successful build. ----- The last CPANPLUS/M::B thing that'd still irk me is M::B runs in-process with CPANPLUS. I've already had this bite me hard with two separate scenarios: 1) CPANPLUS testers aren't able to send any useful pass/failure output to let me know what happened. 2) If you use "cpanp" to try to install more than one package, you get namespace collisions (e.g. "MY::Build" clashes). -- Graham TerMarsch Howling Frog Internet Development, Inc.
