ok. when I get some time again, I shall start from scratch - and ignore
mod_perl for the time being.
Thx for the info.
On Fri, Apr 13, 2012 at 2:09 PM, Jeff Trawick traw...@gmail.com wrote:
On Thu, Apr 12, 2012 at 3:33 PM, Michael Felt mamf...@gmail.com wrote:
Have you found a way to load the
I found, via some googleing and reading - the following from someone who
had been working on getting mod_perl to work with 2.4
svn checkout
http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24/../modperl
Where should I be placing modperl - probably the wrong name for the
directory - to
On Thu, Apr 12, 2012 at 3:33 PM, Michael Felt mamf...@gmail.com wrote:
Have you found a way to load the mod_perl for testing? My attempts to test
using ApacheTest are minimal because ApacheTest does not seem to do much
without it.
mod_perl is not needed at all for testing httpd. I suggest
Have you found a way to load the mod_perl for testing? My attempts to test
using ApacheTest are minimal because ApacheTest does not seem to do much
without it.
2012/4/11 Igor Galić i.ga...@brainsware.org
all tests seems wrong, as we'd skip all tests then. Is there a
way to do explain to
- Original Message -
Have you found a way to load the mod_perl for testing? My attempts to
test using ApacheTest are minimal because ApacheTest does not seem
to do much without it.
I've been testing trunk and right now (or the last time I checked)
mod_perl doesn't compile with
Hi folks,
I'm currently trying to test a very minimal setup of httpd
trunk, and I'm failing because few disables a number of
modules our test suite takes for granted.
Right now I'm stuck in t/modules/alias.t
having a hard time deciding how to proceed since I don't know
the test suite well
Hi Igor,
On 11.04.2012 19:48, Igor Galić wrote:
Hi folks,
I'm currently trying to test a very minimal setup of httpd
trunk, and I'm failing because few disables a number of
modules our test suite takes for granted.
Right now I'm stuck in t/modules/alias.t
having a hard time deciding how to
all tests seems wrong, as we'd skip all tests then. Is there a
way to do explain to the plan that *some* tests require an
additional module?
Don't know. I usually test with reallyall, but most should work as
well.
And few shouldn't?
If that's a feature, perhaps we should put it in the
