Philip M. Gollucci wrote:
Hi,Because of the lines in 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 later time by accident. $mod_perl::VERSION = $mod_perl2::VERSION; $INC{"mod_perl.pm"} = __FILE__;
May be mod_perl.pm in mp1 should be changed to croak if it sees mod_perl2.pm loaded, and the other way around? But since mp1 is not released too often nowaways, how about this alternative solution:
use File::Spec::Functions;
$INC{"mod_perl.pm"} = File::Spec::Functions::devnull();
Apache2::Status Loaded Modules output displaysmod_perl 2.000002 Mon Aug 22 22:55:02 2005 /usr/home/pgollucci/dev/apps/mod_perl-2.0.2/lib/mod_perl2.pm mod_perl2 2.000002 Mon Aug 22 22:55:02 2005 /usr/home/pgollucci/dev/apps/mod_perl-2.0.2/lib/mod_perl2.pmWhich is confusing to me at least.This suppresses the printing of mod_perl.pm which will be especially confusing if you have mp1 and mp2 in the same lib tree.Index: Status.pm =================================================================== --- Status.pm (revision 279713) +++ Status.pm (working copy) @@ -210,6 +210,7 @@ next if $file =~ m:^/:; next unless $file =~ m:\.pm:; next unless $INC{$file}; #e.g. fake Apache2/TieHandle.pm + next if $file eq 'mod_perl.pm'; no strict 'refs'; (my $module = $file) =~ s,/,::,g;
-0, I'd rather see the cause removed than trying to go after every module that relies on the misleading info.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://mailchannels.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
