On Wed, 2005-05-11 at 21:14 +1000, Angus Lees wrote:
> Package: libapache2-mod-perl2
> Severity: important
> Version: 1.999.23-1
>
> The upstream changes document mentions that CGI.pm >= 3.08 is required
> to understand the Great Apache2 Renaming. This version is unavailable
> in Debian, since libcgi-perl is ancient, libcgi-pm-perl no longer
> exists and perl-modules (5.8.4-8) only contains 3.04.
Here's what I sent to thom; I'll record it in the BTS in case some
enterprising developer feels like looking at it:
CGI.pm checks for modperl2, and then includes Apache modules (if found);
this needs to be changed, obviously. This could easily be backported
from 3.08. Throughout the code, there are checks for mod_perl (1 or 2).
The question is, are these APIs the same? If so, backporting 3.08 stuff
is trivial. If not, we'll need to figure out whether to drop mp2 from
sarge, or backport large parts of 3.08 (and any other modules that might
use mod_perl).
Also note that DBI.pm and DBD::mysql seem to check for $ENV{MOD_PERL},
and then:
$DBI::connect_via = "Apache::DBI::connect";
DBI->trace_msg("DBI connect via $DBI::connect_via in
$INC{'Apache/DBI.pm'}\n");
If the mp2 api's changed there, then what mp2 should probably be doing
is setting $ENV{MOD_PERL2} or something, so that client programs can
check for that specifically. This has the added benefit or allowing us
to keep from breaking various perl-modules that assume a certain API
with $ENV{MOD_PERL}. Those modules will just end up not using mod_perl
(not the end of the world).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
