Bug#419952: Missing contents in perl.conf file prevents immediate functionality after enabling of mod in apache

[Gunnar Wolf]

tag 419952 + wontfix
severity 419952 minor
thanks

Hi,

I'm downgrading this bug and tagging is as "wontfix". Your proposed
fix makes it a bit easier, yes, to use mod_perl2 to run Perl scripts
under ModPerl::PerlRun - But in my experience, this is not the usual
case (I do not even recall having ever seen this module!). So... Not
only does this does not solve the problem for every user who
explicitly develops (or uses) Apache Perl modules, but it introduces
an unexpected behaviour to many people who have .pl files anywhere in
their _static_ documents tree.

In my always very humble opinion ( ;-) ), mod_perl is explicitly
installed by people who know what it is about and how to handle
them. When it is implicitly installed by other packages, of course,
_those packages_ should include the needed Apache configuration to get
them working.

Of course, if you disent with me, we can further discuss this.

Greetings,

-- 
Gunnar Wolf - gwolf at gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF