have_module() currently is rather terse when the problem with a
perl module is actually with something the module requires or uses.
here's a patch which will extract a little more info from $@ if it
can, and provide it as part of the message. helpful for tracking
down what is *actually* at fault..
any problems with it? it changes the output of have_module(), so i'm
not committing it without at least offering it for discussion..
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
Index: Apache-Test/lib/Apache/Test.pm
===================================================================
RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/Test.pm,v
retrieving revision 1.80
diff -u -r1.80 Test.pm
--- Apache-Test/lib/Apache/Test.pm 21 May 2004 18:29:51 -0000 1.80
+++ Apache-Test/lib/Apache/Test.pm 24 May 2004 16:18:25 -0000
@@ -217,7 +217,10 @@
eval "require $_";
#print $@ if $@;
if ($@) {
- push @reasons, "cannot find module '$_'";
+ my $why = "cannot use module '$_'";
+ $@ =~ /^(Can't locate.*?) in [EMAIL PROTECTED]/;
+ $why .= " ($1)" if ($1);
+ push @reasons, $why;
}
}
if (@reasons) {
