Hi,
I've attached a diff for Win32 against the current cvs
mod_perl that does three things
- enables ModuleConfig on Win32: this required adding
the ModuleConfig.c to mod_perl.dsp, as well as adding
perl_call_handler and perl_get_startup_pool to mod_perl.def.
I tested this out with a
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 1:10 PM
To: [EMAIL PROTECTED]
Subject: cvs commit: modperl-2.0/Apache-Test/lib/Apache
TestConfigPerl.pm
dougm 01/06/26 10:09:50
Modified:Apache-Test/lib/Apache
On Mon, 9 Jul 2001, Randy Kobes wrote:
Hi,
I've attached a diff for Win32 against the current cvs
mod_perl that does three things
cool, thanks randy, applied to cvs.
I was looking at these because, first of all, wanting to see
if ModuleConfig works on Win32, and also because
On Sun, 8 Jul 2001, Stas Bekman wrote:
Doug, how do we want to change the start_gdb with a more generic code and
decide which debugger is to be used via the command line option and/or env
var?
I suggest that we have 'debug:s' option, where:
--debug
(no value) uses
On Mon, 9 Jul 2001, Geoffrey Young wrote:
die in modperl_startup.pl if modperl_{inc,extra}.pl die
anyway, I thought modperl_extra.pl was supposed to be optional?
it is still optional, but if it exists and dies, then mod_perl should
propagate that. although, the $@ !~ /^Can.t locate/ is
-Original Message-
From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 11:11 AM
To: '[EMAIL PROTECTED]'
Cc: [EMAIL PROTECTED]
Subject: RE: cvs commit: modperl-2.0/Apache-Test/lib/Apache
TestConfigPerl .pm
On Mon, 9 Jul 2001, Geoffrey Young wrote:
On Mon, 9 Jul 2001, Geoffrey Young wrote:
except that my test was dying because modperl_extra.pl didn't exist... I had
to put an (almost) empty file there to get around this warning...
weird. well the pattern was bogus anyhow, i think this will hold up
better for the moment..
Index:
Doug MacEachern wrote:
is anybody still having this problem? if so, can you provide a simple
test case to reproduce?
The problem is, the best test case is to install slash,
http://www.slashcode.com/,
and test against it. It has been pretty haphazard. Most of our users
still
report even using
OK I've finally wrapped my head around how things work at the server
startup.
This [the patch at the bottom] is a crude proof of concept code for
PerlModule. Before I wrap it all nicely, please tell me if that's more or
less how things should be done. This is my first take on adding a new
this is a 1.26 canidate, test reports most appreciated as always..
Changes since 1.25:
I don't have tested this with this version, but there is a problem with
setup of environemt variables when a PerlInitHandler is active. I don't see
in the changes that this is fixed. (See my other mail
I've been thinking about implementing a test ordering scheme for Apache
test and wanted to run it by everyone...
basically from
t/foo.t
t/bar.t
I'd like to be able to specify whether foo.t comes before or after bar.t
(without calling them 1foo.t :)
my reasoning is that it
11 matches
Mail list logo
