Apparent dependency upon mod_perl/Apache::Request?

[byrnereese]

I was provisioned a brand new (dv) instance at mediatemple. It is a CentOS 5.2 (final) OS. I have upgraded all yum packages and even have gotten mod_perlite to function properly.

But getting Movable Type running in this environment is tricky. It boils down to an apparent dependency upon Apache::Request - which is a mod_perl class. Is this true? Is mod_perl a dependency for mod_perlite applications? That doesn't seem right? Or is MT make a poor inference somewhere along the way and trying to route a request through a mod_perl layer because it can't detect CGI or mod_perlite?

Any clues?

[byrnereese]

Upon further investigation I see MT::App has this logic:

if ( $ENV{MOD_PERL} ) {
    require Apache::Request;
    $app->{apache} = $param{ApacheObject} || Apache->request;
    $app->{query} = Apache::Request->instance( $app->{apache},
        POST_MAX => $app->config->CGIMaxUpload );
}

Indicating perhaps that by virtue of mod_perl being installed on the server, Movable Type will attempt to route requests through it. Or do I need to turn off mod_perl all together? or can i disable it for a single virtual host?

[byrnereese]

My mistake. I am dumb. mod_perl was processing the request as it was unbeknowingst to me processing all .pl files.

[byrnereese]

Closing.

[ryandietrich]

Just an fyi to anyone else setting this up. My Ubuntu box needed a bunch of stuff installed to get modperlite up and running.

1. apxs2 (via apache2-threaded-dev)
2. Perl dev (via libperl-dev)
3. Via CPAN, File::Which, Apache::TestMB, Apache::Test, Test-Simple and IPC::Run3

I also got a "random" warning during the compilation process (perl 5.10)

mod_perlite.c:329: warning: passing argument 2 of âPerl_sys_init3â from incompatible pointer type /usr/lib/perl/5.10/CORE/proto.h:4696: note: expected âchar **â but argument is of type âchar * ()[2]â