On Mon, 3 Jun 2002, Gerald Richter wrote:
> avoid all of the mod_perl 2 conditions in Embperl itself. The only thing
> that is missing at the moment and I think you should add it, is a
>
> require Apache::SubRequest ;
>
> otherwise $r -> lookup_uri etc doesn't work.
this is in compat.pm now.
> The otherthing is the test suite, which need to know which version we are
> using and startup.pl need to decide to load Apache::Registry or
> ModPerl::Registry. I currently check $ENV{MOD_PERL}, is there a better way
> to decide, if we are running under mod_perl, something like
> $ModPerl::MajorVersion == 2 would be cool?
you can also use mod_perl (); and check $mod_perl::VERSION
> The question is, why not always install under Apache2?
as mentioned, that is being considered as becoming the default.
> As you said
> Apache::compat maps it to the Apache namespace, so 1.3 modules will continue
> to run? What is the benefit of installing under Apache instead of Apache2?
> Maybe I am wrong, but at the moment I think it would be much easier for the
> normal user to always install under Apache2 and tell them to use
> Apache::compat when they want to use old modules.
the benefit of not installing under Apache2/ is that we don't have to
fiddle with @INC to find the modules. once we can figure out a
clean/sure-fire way to adjust @INC at the proper time(s) to always find
modules relative to Apache2/, we can make MP_INST_APACHE2=1 the default.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
