On Thursday 03 November 2005 17:08, Geoffrey Young wrote:
> > so, please try the attached patch to Apache::Test. hopefully this fixes
> > things once and for all (without breaking more stuff :)
>
> Torsten, any luck with this?
yep, it works:
0 [EMAIL PROTECTED]:~/work/libapreq-1.33$ perl Makefil
> so, please try the attached patch to Apache::Test. hopefully this fixes
> things once and for all (without breaking more stuff :)
Torsten, any luck with this?
--Geoff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
Torsten Foertsch wrote:
> Hi,
>
> is this really necessary in mod_perl2.pm?
I think the decision was made because a ton of legacy applications (like
CGI.pm) would be looking for $mod_perl::VERSION to decide which generation
they were after. whether this is a good idea or not... wel
her than a better documentation of the reasons. Now that it's
clear that it's a bad thing, I think it should be removed.
>> Stas, I actually wanted to change that to
>> $INC{mod_perl2.pm} = __FILE__
>
> but won't that already be set, since this file was already requi
ntation of the reasons. Now that it's
clear that it's a bad thing, I think it should be removed.
>> Stas, I actually wanted to change that to
>> $INC{mod_perl2.pm} = __FILE__
>
> but won't that already be set, since this file
Stas Bekman wrote:
Philip M. Golllucci wrote:
Stas Bekman wrote:
Do you have a URL to this discussion?
http://gossamer-threads.com/lists/modperl/dev/80422
HTH
--
END
--
Philip M. Gollucci
Consultant
E-Mail: [EMAIL PROTECT
Philip M. Golllucci wrote:
Stas Bekman wrote:
Anybody can tell me why the following code was added?
% cat lib/mod_perl2.pm
[...]
# this stuff is here to assist back compat
# basically, if you
# PerlModule mod_perl2
# or take similar steps to load mod_perl2 at
# startup you are protected against
Stas Bekman wrote:
Anybody can tell me why the following code was added?
% cat lib/mod_perl2.pm
[...]
# this stuff is here to assist back compat
# basically, if you
# PerlModule mod_perl2
# or take similar steps to load mod_perl2 at
# startup you are protected against loading mod_perl.pm
Anybody can tell me why the following code was added?
% cat lib/mod_perl2.pm
[...]
# this stuff is here to assist back compat
# basically, if you
# PerlModule mod_perl2
# or take similar steps to load mod_perl2 at
# startup you are protected against loading mod_perl.pm
# (either 1.0 or 1.99) at a
Geoffrey Young wrote:
May I suggest that this exact comment above that line in mod_perl2.pm
prevent the confusion and attempt to fix things?
done. feel free to improve it if it's inadequate.
--Geoff
Okay, I agree with all that. How about also, we add to Apache2::Status
the below patch.
I
> May I suggest that this exact comment above that line in mod_perl2.pm
> prevent the confusion and attempt to fix things?
done. feel free to improve it if it's inadequate.
--Geoff
-
To unsubscribe, e-mail: [EMAI
Geoffrey Young wrote:
Index: mod_perl2.pm
===
--- mod_perl2.pm(revision 164006)
+++ mod_perl2.pm(working copy)
@@ -41,7 +41,7 @@
}
$mod_perl::VERSION = $mod_perl2::VERSION;
-$INC{"mod_perl.pm"} = __FIL
>> Index: mod_perl2.pm
>> ===
>> --- mod_perl2.pm(revision 164006)
>> +++ mod_perl2.pm(working copy)
>> @@ -41,7 +41,7 @@
>> }
>>
>> $mod_perl::VERSION = $mod_pe
Philip M. Gollucci wrote:
Fix the @INC which I caught via the Apache2::Status loaded modules screen:
Index: mod_perl2.pm
===
--- mod_perl2.pm(revision 164006)
+++ mod_perl2.pm(working copy)
@@ -41,7 +41,7
Fix the @INC which I caught via the Apache2::Status loaded modules screen:
Index: mod_perl2.pm
===
--- mod_perl2.pm(revision 164006)
+++ mod_perl2.pm(working copy)
@@ -41,7 +41,7 @@
}
$mod_perl::VERSION = $mod_perl2
15 matches
Mail list logo
