Re: Perl test framework, TestConfig, and debugging A::T

2004-01-15 Thread Stas Bekman
William McKee wrote: On Wed, Jan 14, 2004 at 03:43:59PM -0800, Stas Bekman wrote: OK, I'm working on this conversion and am hitting a roadblock due to mp1 not supporting the PerlSwitches directive. No need to: That's a nice solution for enabling taintmode and warnings, but I was referring to

Re: Perl test framework, TestConfig, and debugging A::T

2004-01-15 Thread William McKee
On Wed, Jan 14, 2004 at 11:21:13AM -0800, Stas Bekman wrote: and Apache::Test-config in perl files: my $dir = catdir Apache::Test::config()-{vars}-{documentroot}, '...', We need better docs for this configuration issue. Patches are very welcome. I'm not sure I follow your comment. Am I

[STATUS] (flood) Wed Jan 14 23:46:07 EST 2004

2004-01-15 Thread Rodent of Unusual Size
flood STATUS: -*-text-*- Last modified at [$Date: 2003/07/01 20:55:12 $] Release: 1.0: Released July 23, 2002 milestone-03: Tagged January 16, 2002 ASF-transfer: Released July 17, 2001 milestone-02: Tagged August 13,

[STATUS] (perl-framework) Wed Jan 14 23:46:14 EST 2004

2004-01-15 Thread Rodent of Unusual Size
httpd-test/perl-framework STATUS: -*-text-*- Last modified at [$Date: 2002/03/09 05:22:48 $] Stuff to do: * finish the t/TEST exit code issue (ORed with 0x2C if framework failed) * change existing tests that frob the DocumentRoot (e.g.,

Re: Perl test framework, TestConfig, and debugging A::T

2004-01-15 Thread William McKee
On Wed, Jan 14, 2004 at 08:41:01PM -0800, Stas Bekman wrote: Cool, now I get the thing running. Great. Are you getting any failures? Please read my notes in testnotes.txt. What is this diff? Should I apply it against [1]? Why not just update your snapshot? Sorry, this is against the

more sticky preferences issues...

2004-01-15 Thread Geoffrey Young
ok, here's my latest problem... given a 3rd party module installation $ perl Makefile.PL -apxs /foo/bin/apxs two issues arrive 1) $HOME/.apache-test is created when the tests are run, not when the module is installed. which means that even without any actual installs 2) -apxs is

Re: [Fwd: Re: Modperl 2.0 Not finding correct *.conf]

2004-01-15 Thread Geoffrey Young
Stas Bekman wrote: any objections for this patch? -if (-e $result) { -debug $file successfully resolved to existing file $result; well, you're removing the file check in favor of a directory check. in the interests of debugging, I'd probably like to preserve the check and throw

Re: [Fwd: Re: Modperl 2.0 Not finding correct *.conf]

2004-01-15 Thread Stas Bekman
Geoffrey Young wrote: Stas Bekman wrote: any objections for this patch? -if (-e $result) { -debug $file successfully resolved to existing file $result; well, you're removing the file check in favor of a directory check. in the interests of debugging, I'd probably like to preserve

Re: more sticky preferences issues...

2004-01-15 Thread Stas Bekman
Geoffrey Young wrote: ok, here's my latest problem... given a 3rd party module installation $ perl Makefile.PL -apxs /foo/bin/apxs two issues arrive 1) $HOME/.apache-test is created when the tests are run, not when the module is installed. which means that even without any actual installs I think

Re: Perl test framework, TestConfig, and debugging A::T

2004-01-15 Thread Stas Bekman
William McKee wrote: On Wed, Jan 14, 2004 at 08:41:01PM -0800, Stas Bekman wrote: Cool, now I get the thing running. Great. Are you getting any failures? Please read my notes in testnotes.txt. Yes. I will look at the failures soonish. What is this diff? Should I apply it against [1]? Why not

Re: [Fwd: Re: Modperl 2.0 Not finding correct *.conf]

2004-01-15 Thread Geoffrey Young
In any case, adding a check for a file is fine with me as long as you s/warning/debug/, so it won't appear in the normal output and users don't send false complaints. How about adding it as an extra check on top of this patch? that all sounds fine. --Geoff

Re: more sticky preferences issues...

2004-01-15 Thread Geoffrey Young
which means that even without any actual installs I think you didn't finish the sentence? which means that even without any actually installs [2] :) I think because we test only for httpd's setting. that must be the reason. Try passing -httpd instead for now. I will I know lots