http://search.cpan.org/~phoenix/Taint-0.09/Taint.pm
is the one I'm familar with - pure perl and different than the one
from dan.
Ah, that's cool. But as I said that 0.09 fails a bunch of tests for me.
I get the same failures. I'm not a Test::Harness expert, but it looks like
lots of the fail
Geoffrey Young wrote:
[EMAIL PROTECTED] wrote:
randyk 2003/11/07 00:48:21
Modified:perl-framework/Apache-Test Makefile.PL
perl-framework/Apache-Test/lib/Apache TestConfig.pm
ah, here it is :)
just as a general note, if you noticed, this commit had multiple targets
Geoffrey Young wrote:
[...]
And a whole Taint.xs
http://search.cpan.org/src/DSUGAL/Taint-0.07/Taint.xs
(For some reason search.cpan.org has the old version, as there is 0.09)
And it fails a bunch of test with any 5.8.x perl
http://search.cpan.org/~phoenix/Taint-0.09/Taint.pm
is the one I'm famil
[EMAIL PROTECTED] wrote:
randyk 2003/11/07 00:48:21
Modified:perl-framework/Apache-Test Makefile.PL
perl-framework/Apache-Test/lib/Apache TestConfig.pm
ah, here it is :)
just as a general note, if you noticed, this commit had multiple targets -
both the modperl-2.0 an
Geoffrey Young wrote:
This won't affect mp2, since we already require 5.6.0, but for
standalone installs it'll fetch the newer version.
So add PREREQ_PM and +1 to commit.
I didn't see this in the commit email, so I'm guessing it didn't make it
to the release candidate.
Nope, Randy committed it
This won't affect mp2, since we already require 5.6.0, but for
standalone installs it'll fetch the newer version.
So add PREREQ_PM and +1 to commit.
I didn't see this in the commit email, so I'm guessing it didn't make it to
the release candidate.
I'm ok with this going in over the weekend, s
a release candidate for Apache-Test 1.06 is now available. 1.06 is the
version of Apache-Test that will ship with mod_perl 1.99_11.
http://perl.apache.org/~geoff/Apache-Test-1.06-dev.tar.gz
please take the time to excercise the candidate through all your existing
applications that use Apache
a release candidate for mod_perl 1.99_11 is now available for testing. note
that 1.99_11 will be required for users running perl 5.8.2.
please grab the candidate from
http://perl.apache.org/~geoff/mod_perl-1.99_11-dev.tar.gz
and report back successes or failures. when reporting failures, pl
FYI: Geoff added -startup_timeout || $ENV{APACHE_TEST_STARTUP_TIMEOUT}
whoops - forgot those commits don't go here :)
--Geoff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Geoffrey Young wrote:
hi all
we're about to enter into another release cycle for mod_perl 2.0, so I'd
like to ask for a code freeze until the release candidate has been
rolled, then allow only fixes to reported RC problems until 1.99_11 is
official.
1.99_11-RC1 should be on it's way shortly.
R
Geoffrey Young wrote:
Stas Bekman wrote:
The thing that triggered my recent post about the ridiculously slow
perl_clone is that my smoke tests almost always fail to run the worker
mpm, if my machine is busy running some other heavy tasks at the same
moment. 60 secs is just not enough to start
hi all
we're about to enter into another release cycle for mod_perl 2.0, so I'd
like to ask for a code freeze until the release candidate has been rolled,
then allow only fixes to reported RC problems until 1.99_11 is official.
1.99_11-RC1 should be on it's way shortly.
--Geoff
--
the attached patch makes it possible to use -bugreport with the
Apache::TestRun(Perl)->generate_script() form
sorry, I meant to include examples. with this patch, you can use the
following formats in your Makefile.PL
# scalars are printed in the post-error banner
Apache::TestRun(Perl)->generat
[EMAIL PROTECTED] wrote:
stas2003/11/05 01:52:18
Modified:.Makefile.PL Changes
ModPerl-Registry/t TEST.PL
lib/ModPerl TestRun.pm
Log:
When 'make test' fails we now print the info on what to do next
the attached patch makes it possible to
Stas Bekman wrote:
The thing that triggered my recent post about the ridiculously slow
perl_clone is that my smoke tests almost always fail to run the worker
mpm, if my machine is busy running some other heavy tasks at the same
moment. 60 secs is just not enough to start the worker server's te
Rafael Garcia-Suarez wrote:
Stas Bekman wrote:
Scott gets the getppid test failing with mp2-cvs/5.8.0 but I can't reproduce
it. I think this is because RH ships a fake 5.8.0. It says MAINT18379 which
dates 27 Dec 2002 (5 months after 5.8.0 was released)
http://public.activestate.com/cgi-bin/perl
Stas Bekman wrote:
>
> Scott gets the getppid test failing with mp2-cvs/5.8.0 but I can't reproduce
> it. I think this is because RH ships a fake 5.8.0. It says MAINT18379 which
> dates 27 Dec 2002 (5 months after 5.8.0 was released)
> http://public.activestate.com/cgi-bin/perlbrowse?patch=18379
Stas Bekman wrote:
perl-5.8.2, which means that we need to make a new mod_perl 2 release
(older versions may have problems with 5.8.2) asap.
Once I'm done with fixing the read() and PerlIOApache_read() functions
I'll start preparing the 1.99_11 candidate so if there is anything
urgent that you
Randy Kobes wrote:
Hi,
There's a couple of places where /dev/null is used
which, on Win32, will fail if a directory /dev isn't
present. This diff:
[...]
uses devnull() of File::Spec to specify something that
will work in general on Win32 (just a file called "null").
That's cool, Randy. There is o
Hi,
There's a couple of places where /dev/null is used
which, on Win32, will fail if a directory /dev isn't
present. This diff:
=
Index: lib/Apache/Build.pm
===
RCS file: /home/cvs/
Randy Kobes wrote:
On Thu, 6 Nov 2003, Stas Bekman wrote:
Randy Kobes wrote:
very neat! A few more comments:
=
Index: Makefile.PL
===
[...]
+sub fetch_apxs {
+my $prefix =
21 matches
Mail list logo
