Skip Menu |

This queue is for tickets about the CGI-Application-Dispatch CPAN distribution.

Report information
The Basics
Id: 37210
Status: resolved
Priority: 0/
Queue: CGI-Application-Dispatch

People
Owner: Nobody in particular
Requestors: FRIEDO [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 2.12
Fixed in: (no value)



Subject: Build.PL fails without Apache::TestMB
The Build.PL script packaged with CA::Dispatch 2.12 checks to see if Apache::TestMB is available and if not, it tries to build with Module::Build. Except it doesn't actually load Module::Build. # perl Build.PL Can't locate object method "new" via package "Module::Build" (perhaps you forgot to load "Module::Build"?) at Build.PL line 2. A .diff is attached to fix the problem. Mike Friedman
Subject: Build.PL.diff
1c1,4 < my $build_pkg = eval "require Apache::TestMB" ? 'Apache::TestMB' : 'Module::Build'; --- > my $build_pkg = eval "require Apache::TestMB" ? 'Apache::TestMB' > : eval "require Module::Build" ? 'Module::Build' > : die 'No builder found'; >
Just realized this seems to be fixed in 2.13_02, but that's still marked as a DEVELOPER RELEASE. Perhaps it's time to make that an official release? CPAN.pm still downloads 2.12 by default, so presumably lots of people are still running into this. Mike On Sun Jun 29 19:30:53 2008, FRIEDO wrote: Show quoted text
> The Build.PL script packaged with CA::Dispatch 2.12 checks to see if > Apache::TestMB is available and if not, it tries to build with > Module::Build. Except it doesn't actually load Module::Build. > > # perl Build.PL > Can't locate object method "new" via package "Module::Build" (perhaps > you forgot to load "Module::Build"?) at Build.PL line 2. > > > A .diff is attached to fix the problem. > > > Mike Friedman
On Mon Jun 30 08:44:37 2008, FRIEDO wrote: Show quoted text
> Just realized this seems to be fixed in 2.13_02, but that's still marked > as a DEVELOPER RELEASE. Perhaps it's time to make that an official > release? CPAN.pm still downloads 2.12 by default, so presumably lots of > people are still running into this.
Good point. I'll try and do that today.
This is fixed in the 2.13 release.