On Thu, Nov 15, 2001 at 09:58:53AM -0800, Doug MacEachern wrote:
> i would really like to see something that could run automated tests for:
>
> perl flavors:
> -5.004_xx (mod_perl-1.x only)
> -5.005_03 (mod_perl-1.x only)
> -5.6.1 vanilla
> -5.6.1 ithreads
> -bleed vanilla
> -bleed ithreads
> -va
> maybe what we should do is have Apache->server_root_relative that behaves
> just like 1.x in Apache::compat and have 2.0's function be named
> Apache::server_root() which returns ap_server_root if fname == NULL and
> calls ap_server_root_relative() otherwise. this would also fix the
> current c
On Thu, 15 Nov 2001, Stas Bekman wrote:
> ok, that sounds good. I say we should change it. My reasoning is that
> the API never defined the case where fname==NULL, so it wasn't a part of
> the public API and users weren't supposed to use this method with
> fname==NULL => we can safely add t
i would really like to see something that could run automated tests for:
perl flavors:
-5.004_xx (mod_perl-1.x only)
-5.005_03 (mod_perl-1.x only)
-5.6.1 vanilla
-5.6.1 ithreads
-bleed vanilla
-bleed ithreads
-various other flavors as needed
=> mod_perl-1.x + apache-1.3 + all perl flavors
apach
>
> But since there are only a handfull of people working on
> mod_perl right now,
> would it really be THAT usefull?
I would think so. I've been compiling bleedperl, mod_perl, and apache from
CVS on a nightly basis for almost a year now. over that time I've caught a
few changes to bleedper
