Doug MacEachern wrote:
> i also saw the same mime.types problem, triggered by the failed require of
> perlrequire.pm, you'll need to rm t/conf/*.conf
basically the problem occurs for failures during configure,
and the system doesn't have a way to check the the whole configuration is in place.
I was thinking about creating some checkpoint to make sure that config files
are always complete.
is there still a problem with perlrequire? i.e. APACHE_TEST_CONFIGURE?
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
