Hi, I actually jumped in the code to try and fix the bug you report - Actually, Apache::DBILogger is a very simple module, and the patch seems trivial as well - Probably, as easy as this:
--- DBILogger.pm.orig 2007-02-26 09:44:09.000000000 -0600
+++ DBILogger.pm 2007-02-26 09:44:18.000000000 -0600
@@ -2,7 +2,7 @@
require 5.004;
use strict;
-use Apache::Constants qw( :common );
+use Apache2::Const qw( :common );
use DBI;
use Date::Format;
However, I seem to have hit an (unrelated?) Apache2 bug in Sid - I'll
take a look on this.
Anyway, as soon as I get this working (either with Sid or with Sarge
Apache2, which are -again- not exactly API-compatible), I'll post a
patch for the upstream author - and find a sane path on how to fix
this, so we don't have two packages just replicating
functionality. Maybe it will be sane to do:
BEGIN {
eval "use Apache::Constants qw(:common)";
if ($@) {
eval "use Apache2::Const qw(:common)";
if ($@) {
die "Not under Apache, not under Apache2?\n$@";
}
}
}
Anyway, I'll do a couple of checks, and then debug why it's not
working in Sid ;-)
Greetings,
--
Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
signature.asc
Description: Digital signature
