David Wheeler wrote:
On Jun 25, 2004, at 8:31 AM, David Wheeler wrote:
blarg. a revised candidate is in the same place. sorry about that.
Thanks, I'll try it later today.
Works great for me! Only issue I'm seeing is that
Crequests_redirectable = 0 isn't working on one of my
:
add -no-httpd runtime option to allow tests to run without configuring,
starting, or stopping Apache. this essentially provides a direct
Test::Harness interface through t/TEST, useful for running single tests
that do not depend on Apache. [Geoffrey Young]
Add support for Module::Build
hi all.
we have been using Apache-Test to run our entire testing framework, which is
great - we can mix and match apache-related and non-apache related tests
under the same testing tree and it all works without a hitch.
the only problem is that when working on small testing units that don't
hi all...
as suggested by stas in a recent thread, it's about time we gave david
commit access to the perl-framework - he has been actively helping with the
project for as long as I can remember, from mac-specific stuff to lots of
great work on the (often thin) docs. and now he is working
Stas Bekman wrote:
David Wheeler wrote:
On Jun 23, 2004, at 9:02 AM, Stas Bekman wrote:
Now committed with a few minor tweaks, please test it since I don't
know how to test it. Thanks David.
Cool, thanks. What do you need to be able to feel comfortable/ready to
release it?
As I
+1
:)
+if ($self-{opts}-{'no-httpd'}) {
+warning skipping configuration: -no-httpd specified;
may be it's better to sayskipping httpd configuration?
sure, that's fine.
+return
please don't forget ; if } is on the next line.
oops :)
may be use -nohttpd, so
I think it's OK to add any extra logging in the verbose mode though
(when -verbose is passed) if you find it helpful as a developer. The
verbose mode is for developers and for when users have problems, so any
extra useful info is a goodness.
yeah, that's a good idea.
nevertheless, it
Rodent of Unusual Size wrote:
have_module() currently is rather terse when the problem with a
perl module is actually with something the module requires or uses.
here's a patch which will extract a little more info from $@ if it
can, and provide it as part of the message. helpful for
so you're arguing that we should write out the sticky files, even if the
user doesn't ever want them interfering?
I'm not arguing at all. It's just when
APACHE_TEST_NO_STICKY_PREFERENCES=1 and no arguments passed, the logic
is broken. The program gets into a loop it can't break out of.
just some ideas.
Yeah, but we still have a problem to solve.
well, go ahead and remove the lack of save then, if you're certain that it
fixes the problem you're having. I don't really have the time at the moment
to implement an entire new mechanism. actually, I'd rather stay away from
Please show us the verbose trace:
t/TEST -trace=debug
including the part where you completed the interactive questions, and it
brought you back to interactive config again.
ok, the plan was to roll an official release this afternoon (as in now).
what's the feeling on this? release as is
The URL
http://perl.apache.org/~geoff/Apache-Test-1.11.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GE/GEOFF/Apache-Test-1.11.tar.gz
size: 116279 bytes
md5: 6a0e30ed99d84b683138b160e30ad474
--Geoff
Changes since 1.10:
if we fail to match the Apache revision (which is OK at
blargh - cut and paste error. the subject should read Apache-Test-1.11.
--Geoff
Stas Bekman wrote:
Geoff, why did you make APACHE_TEST_NO_STICKY_PREFERENCES prevent from
saving autoconfig?
however it's done, I want an option wereby absolutely nothing sticky is ever
generated or used. the don't touch my system option was my goal, which
really isn't unreasonable.
cross-posting to test-dev@, which is probably where we ought to discuss the
gory details...
Failed Test Stat Wstat Total Fail Failed List of Failed
at this point the test part of the perl-framework is
Use of uninitialized value in concatenation (.) or string at
/home/sctemme/asf/perl-framework/Apache-Test/lib/Apache/TestRequest.pm
The single request for /index.html is the framework's ping to see if
the server has started. It is not part of the errordoc tests, which
suggests that
For example this
does the trick:
Index: Apache-Test/lib/Apache/TestRun.pm
===
RCS file:
/home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/TestRun.pm,v
retrieving revision 1.166
diff -u -r1.166 TestRun.pm
---
+# _show_results() calls uses calls die() under a few
conditions,
calls uses calls ? :)
I swear something is wrong with me lately...
--Geoff
hi all
a while ago Ken Coar brought up that Apache-Test doesn't print the final
test count when there are errors. that is, we currently do this:
# Failed test 20 in t/apache/contentlength.t at line 54 fail #10
FAILED tests 2, 6, 10, 14, 16, 18, 20
Failed 7/20 tests, 65.00% okay
Failed
Not sure what you are talking about above, the only difference between
the two is in line:
blarg, cut and paste error.
without my patch, it looks like this (note it's 1.3)
[EMAIL PROTECTED] perl-framework]$ t/TEST t/apache/contentlength.t -v
/apache/1.3/dso/perl-5.8.4/bin/httpd -d
Got it. Why not just do this:
return unless $_[0] =~ /^Failed/i; #dont catch Test::ok failures
+print $_[0];
truthfully, I spent far too long trying to figure out why the die() wasn't
cascading. once I got it I just patched it and let the patch fly without
too much
I don't understand why did you have this problem (what did you have in
@INC?), but I think that this just works around the problem. It's better
to go up to where $self-{inc} is getting set and not let invalid values
in, so if you use $self-{inc} you won't have to workaround again.
I was
hi all
I've managed to figure out at least preliminary support for using Test::More
as the backend for Apache::Test. attached is a patch as well as a tarball
that uses a few Test::More features in it. I may have missed a few of the
finer features of Test::More, but it seems to do what I need it
whichever is fine with me. Though please explain where did you take that
standard from? I think most modules follow the followinig import
convention:
- a word 'foo' usually means symbol and you'd expect to be able to use
it in a form of ([EMAIL PROTECTED])foo.
- a tag ':foo' means,
The main problem is the dependency which we we don't want to create in
Apache-Test.
yes, I agree. but I think that something like this would be great, as it
would keep users from needing to jump through a bunch of hoops just to
prevent redefined warnings.
--Geoff
Index: lib/Apache/Test.pm
I like that idea of adopting all of T::M. However, does T::M have a
comparable function to t_cmp that gives the expected and received
values? I *really* like the verbose output that t_cmp gives!
is() is similar in many ways to t_cmp() except it doesn't support array
comparisons, regular
ok t_cmp (
undef,
get_undef,
Retrieve undef from subroutine
);
# expected: undef
# received: Retrieve undef from subroutine
not ok 1
get_undef is slurping up the text as an argument. call it as get_undef()
instead (nobody really uses the
Geoffrey Young wrote:
ok t_cmp (
undef,
get_undef,
Retrieve undef from subroutine
);
# expected: undef
# received: Retrieve undef from subroutine
not ok 1
get_undef is slurping up the text as an argument. call it as get_undef()
instead
right, I think I got that. but that requires knowing the hard-coded
path.
That's what Ken wanted
ok, but just because you get substitution doesn't mean you have to use it :)
perhaps I wasn't clear enough, but the proposed httpd.extra.conf.in
would be
appended to the generated
By splicing you mean 'Include ken_extra.conf' from t/conf/httpd.conf?
Yes, but have_module() doesn't look it up in any of the conf files, it
looks it up from the config object $cfg-{modules} which get populate
with available modules when the config is generated, and it only scans
the
Something is not right here, Geoff. It require()s *only* if
IS_MOD_PERL_2 is true. Which must have Apache::Build present. I suggest
that you try to revert it and find the real cause of the problem, rather
than hide it. Thanks.
ah, I see what's going on. I removed all Apache stuff but
Rodent of Unusual Size wrote:
Randy Kobes wrote:
If you put the compiled modules in place, and then run
'nmake test', is the problem that things get cleaned out
first (erasing the binaries), or that it just tries to
recompile things? On my system (which has VC++), 'nmake
test' first cleans
Rodent of Unusual Size wrote:
Rodent of Unusual Size wrote:
specifically what operations need make or nmake? i need to
know so i can provide appropriately-prepared files so it
won't try to run it. this is so i can run it on systems
that don't have a developer environment installed..
% t/TEST -help
...
and in case it's not obvious (and for the archives) the '...' represents a
slurry of options from TestRun.pm, whereas the shown 'configuration options'
represent those from TestConfig.pm. I was wondering where -preamble and
some others were and it took me a minute :)
Stas Bekman wrote:
Rodent of Unusual Size wrote:
Stas Bekman wrote:
does this make any difference/
perl Makefile.PL -apxs K:/Coar/Apache/Server-1.3/bin/apxs.pl -httpd
K:/Coar/Apache/Server-1.3/bin/Apache.exe
yes, it made a difference -- but it still didn't work. it now
specifies
hi all
I'm _still_ having problems with sticky preferences. unfortunately, I don't
have the time atm to locate the specifics, but basically I was trying to
compile a 1.3 static build (without mod_so) using -httpd. while A-T found
the proper httpd, LoadModule statements that pointed to my last
$ENV{APACHE_TEST_STARTUP_TIMEOUT} now supersedes -startup_timeout
[...]
What's the reason for this change?
it was a follow up from something on modperl@
I almost always expect that command
line arguments supercede env variables.. i.e.
$ CVSROOT=foo cvs -d bar co foo
Bad CVSROOT:
+my $dversion = $self-server-dversion;
+if ($dversion eq '-DAPACHE1') {
that's '-D APACHE1' in current cvs, no?
--Geoff
so, it looks like an issue with your wrapper and not A-T
core, yes?
no. if i run only a test script that passes completely, i get
t/modules/accessok
All tests successful.
Files=1, Tests=408, 4 wallclock secs ( 3.13 cusr + 0.43 csys = 3.56 CPU)
if i run only a script that fails,
Bail out!
to standard output. Any message after these words will be
displayed
by Test::Harness as the reason why testing is stopped.
I haven't tested whether this really works in A-T, but I see no reason
why it shouldn't.
I tried to use it when I was
t/modules/expires.t924 4.35% 13 21 33 45
14 subtests skipped.
and that's it.
oh, I see what you mean, you're missing the
Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
line.
are you using an older version of perl perhaps?
yep,
Stas Bekman wrote:
We would like to release Apache::Test 1.08. It includes multiple changes
and improvements, therefore we need your help to test it and report any
problems you may have noticed.
http://apache.org/~stas/Apache-Test-1.08-dev.tar.gz
I'm getting a strange error from 5.6.1
sub config_defines {
+my $self = shift;
+
my @defines = ();
for my $item (qw(useithreads)) {
@@ -88,7 +90,9 @@
push @defines, -DPERL_\U$item;
}
-push @defines, map { -D$_ } split ,
shift-{config}-{vars}-{defines};
+if
in my case, it's possibly my wrapper that's gobbling the line. for
pity's sake, why it that going to stderr when everything else is going to
stdout?
erk. now i'm seeing it, but *only* if all of the tests are successful.
i need to see it regardless, and including the
-$file ||= 'SKIP';
+$file ||= 't/SKIP';
excellent, thanks for tracking that down.
we just need to be a bit more platform independent. if you could verify
that the attached patch works ok for you, I'll commit it.
--Geoff
Index: lib/Apache/TestHarness.pm
1. is it possible to run the suite *without* doing a 'make install'?
in my development environment i discovered that i had to do that
in order oget rid of some cruft left behind from having done a
'make install' in the past. however, i'd prefer to not have to
force the
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
oops. forgot to add the class up top. guess I'm not quite with it today yet :)
--Geoff
Index: lib/Apache/TestHarness.pm
===
RCS file:
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
Geoff, you are making a good point of removing the hardcoding of t/
towards the idea of being able to split the test suite.
well, it's an idea that we're all working toward, yourself included :)
is there really no way to pass additional -D switches to the server? I
can't see any, so unless I'm missing it...
--Geoff
Index: lib/Apache/TestConfig.pm
===
RCS file:
Stas Bekman wrote:
I'd like to get a new A-T out of the door. There were a *lot* of tweaks
and new features added since the last release. It'd be nice to see
whether users are happy with them, before we get a new mp2 release out.
sounds like a plan.
--Geoff
$vars-{proxyssl_url} ||= '';
+$self-{defines} ||= '';
oops, make that $vars :)
--Geoff
Joe Orton wrote:
On Fri, Feb 20, 2004 at 01:30:03PM -0500, Geoffrey Young wrote:
is there really no way to pass additional -D switches to the server? I
can't see any, so unless I'm missing it...
Ooh, cool, I tried to add that feature earlier in the week too (and
didn't come up
+(my $generated = $File::Find::name) =~ s/\.in$//;
+push @need_update, $generated
+unless -e $generated -M $generated -M $File::Find::name;
-if (my $extra_conf = $self-generate_extra_conf) {
-for my $file (@$extra_conf) {
-
you flipped the logic here. it needs to be
unless -e $generated -M $generated -M $File::Find::name
I don't think so. The two snippets you quoted above aren't the same.
I've changed the functionality and changed the order of the arguments.
ok, I see now. when I ran my own logic
sub vhost_socket {
-my $module = shift;
+my ($module, $nossl) = @_;
local $Apache::TestRequest::Module = $module if $module;
my $hostport = hostport(Apache::Test::config());
@@ -224,7 +224,7 @@
my($host, $port) = split ':', $hostport;
my(%args) = (PeerAddr
Well, it gets my vote. If it were to be an argument, it would have to
be stripped out of @_ before being passed through to LWP, which sounds
like it could get messy.
ok, give this a whirl and see if it works for you.
--Geoff
Index: Apache-Test/lib/Apache/TestRequest.pm
Joe Orton wrote:
On Wed, Feb 18, 2004 at 10:40:51AM -0500, Geoffrey Young wrote:
Well, it gets my vote. If it were to be an argument, it would have to
be stripped out of @_ before being passed through to LWP, which sounds
like it could get messy.
ok, give this a whirl and see if it works
So it'll look like:
[warning] setting ulimit to allow core files
ulimit -c unlimited;
/home/stas/perl/5.8.1-ithread-nouseshrplib/bin/perl5.8.1 t/TEST
-trace=debug
[debug] isolated httpd_info VERSION = Apache/2.0.49-dev
[...]
[crit] generating conf/httpd.conf
that's really a critical
Stas Bekman wrote:
The following patch, allows a graceful exit from 'make test' (so that
CPAN.pm and other clients can continue w/ installation) if users fail to
provide the path to httpd or running under root and we figure out that
apache can't access the files w/ nobody (or some other
+@_ ? @{ config()-{vars} }{ @_ } : config()-{vars};
wow, a slice in the wild. cool :)
--Geoff
Stas Bekman wrote:
David Wheeler wrote:
On Jan 28, 2004, at 2:21 PM, Stas Bekman wrote:
Then for now I'll just use:
my $serverroot = Apache::Test::config()-{vars}{serverroot};
the idea is to get away from that - it's way too verbose to be conventient.
AUTOLOAD is okay with me. It's
Stas Bekman wrote:
David Wheeler wrote:
On Jan 23, 2004, at 12:21 PM, Stas Bekman wrote:
If you really want to, we could install Apache::Test::AUTOLOAD
which will map $AUTOLOAD to
Apache::Test::config()-{vars}-{$AUTOLOAD}, so you could say:
Apache::Test::serverroot
Or, I imagine,
I'll wait for a blessing from Geoff and then try to fix the mp2 and
httpd-test/perl-framework tests first. If successful, then it'll be in
the next release.
yes, lots of breakage there.
I think what I'd like to see is an easier way to get the ServerRoot (and
DocumentRoot?) than
So let me see if I follow you. The request script is the client and
should output the test results. The response handler is handling the
server-side requests. It can send information back to the client to
output. It looked, though, like Geoff was using examples such as plan
$r, tests=9 in
I would appreciate some recommendations
for books that explain the big picture view of testing. Have any titles
on your bookshelf that you'd suggest for someone like myself? I don't
know of any books that discuss testing specifically from a Perl
perspective. Do you?
ORA had one in the works,
now, Apache-Test gets tricky. it _also_ makes sure that the server
response
gets funneled to Test::Harness if you use the plan $r, tests = 9 syntax
I think this makes it sound trickier than it needs to; AIUI the feeding the
results back to Test::Harness is nothing to do with what syntax
well, it's important if you're writing an API, not merely testing CGI
scripts or the like. for instance, suppose you have a class that subclasses
mod_perl. if you plan'd and ok'd things from a PerlHandler then you could
do things like
isa_ok($r, 'My::Class');
which you can't really do
There's one last piece that I'm still unclear on which your article did
not mention--reponse handlers. Is this where the two paths diverge? I'm
not sure that I see much difference between the way you do it and the
highly magical stuff.
well, that's the next step. instead of calling plan()
I see why you call this code magical. It's definitely a step beyond my
understanding and probably beyond my needs for now.
:)
OK, I'm beginning to see now. I was able to take my revised skeleton and
replace Apache::Test with Test::More. I had to modify the plan line to
remove the
Honestly, I am trying my best. The problems I am encountering are
changing perspective from a cgi to a mod_perl framework which thus
entails learning lots more about the Apache server than I've ever known
before. My apologies if you think these questions are inane or
off-topic.
no, I'm
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
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
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
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
André Malo wrote:
* [EMAIL PROTECTED] wrote:
Modified:perl-framework/t/modules include.t
Log:
cross-version updates
Thanks.
You just forgot to commit echo3.shtml and size.shtml :-)
whoops, sorry about that - I guess I've been away from this for a while :)
a fresh checkout
[EMAIL PROTECTED] wrote:
nd 2004/01/12 08:04:50
Modified:perl-framework/t/modules autoindex.t
not to be a pest, but I still have this patch floating around. if there's
no interest I'll just scrap it.
--Geoff
Index: t/modules/include.t
$ perl Makefile.PL MP_APXS=/apache/2.1/prefork/perl-5.8.2/bin/apxs
...
Configuring Apache/2.1.0-dev mod_perl/1.99_13-dev Perl/v5.8.2
$ make make test
...
using Apache/2.0.49-dev (prefork MPM)
waiting 120 seconds for server to start: .httpd: module mod_perl.c
is not
compatible with
Yes, thank you Geoff, I've noticed that too late. And my mail server was
down most of the day :(
:)
I think I have fixed these problems now.
What bothers me is the call to default_httpd, which may pick a wrong
server. So I've removed it. It is used in the interactive config, to
help
Donald Doane wrote:
Can someone please confirm whether or not apr_psprintf is thread safe.
Thank you.
sorry, wrong list. try [EMAIL PROTECTED]
--Geoff
-my $has_version = $module-VERSION || 0;
-return 1 if $has_version = $version;
+return 1 if eval { $module-VERSION($version) };
Are you sure you haven't dropped something here? why did you remove the
comparison line?
becuase it's both wrong and unnecessary:
VERSION
Can you please run t/TEST -debug=trace and see which TestConfigData.pm
is loaded? what's inside of it? May be the simple solution is not to
load custom_config when running from inside modperl-2.0? I think that's
the best solution.
I've already cleaned everything out for today, but I'll do
committed. looking forward to hear about the odd parts.
the first thing that strikes me is that when I build mod_perl with
MP_APXS=/foo/bin/apxs then make make test I get the dialogue asking me to
choose httpd and apxs binaries.
I don't think we want a prompt for the mod_perl test suite - it
Geoffrey Young wrote:
committed. looking forward to hear about the odd parts.
the first thing that strikes me is that when I build mod_perl with
MP_APXS=/foo/bin/apxs then make make test I get the dialogue asking me to
choose httpd and apxs binaries.
I don't think we want a prompt
Stas Bekman wrote:
Moreover the prefix
ideally should be: APACHE_TEST_ and not APACHE_, since we already have a
bunch of env vars which start with APACHE_TEST_
Though I'm in favor to just drop them, making
everybody move to the better API.
+1
--Geoff
William McKee wrote:
On Mon, Dec 22, 2003 at 04:06:02PM -0800, Stas Bekman wrote:
Use this archive instead:
Thanks for the link.
Hmm, are you sure you've spelled things right? That's t/logs/error_log. Do
you get anything at all written to it?
Yes, I do get some output written
However, I do like the idea of keeping the server
running since it takes several seconds for my slow system to bring it
up. Running `make t/TEST -run-tests` seems to work fine though.
excellent. I don't use that feature myself, so it's good to know it's
working for people :)
--Geoff
the fsize test fails in 1.3, because the abbrev computation is different (and
the files are so *small* :-)
ok, that is TODO on 1.3 now.
The flastmod test fails on my box because of weird timezone problems.
POSIX::strftime() and mod_include's strftime produce different timezone
strings
well, since I know andre is paying attention, I thought I'd start with
mod_include :)
ok, I made some adjustments to t/modules/include.t to accommodate 1.3, 2.0,
and 2.1. hopefully, all I did was shuffle things around so that it's easier
to keep track of the three cases: proper behavior,
Just to add to the concern Bill has voiced, there is a risk of fixing
testing here. You see that the sub-tests have failed only if you run in
the verbose mode. Most people won't do that, and will miss those
failures, thinking that everything is proper.
hmm, what gives you that impression?
hi all
t/apache/limits.t has one failure on Apache 1.3 - a chunked body that
exceeds the limits. 2.0/2.1 returns 413 (entity too large) while 1.3
returns 400 (bad request).
after looking at the code in 1.3 I think this is intentional -
ap_get_client_block specifically handles this condition,
hi all
currently, the perl-framework for 1.3, 2.0, and cvs fail miserably for me,
and have for some time.
1.3)
Failed TestStat Wstat Total Fail Failed List of Failed
---
apache/chunkinput.t
André Malo wrote:
* Geoffrey Young [EMAIL PROTECTED] wrote:
modules/include.t 9 2304?? ?? % ??
what does this null information mean?
pretty much that the script died before it could complete. for 2.1, for
instance, it's a result of this warning
Use of bare
Use of bare to mean is deprecated at modules/include.t line 120.
which is probably new to 5.8.2.
Interesting. doesn't occur within include.t. So it happens within the
framework?
hmm, perhaps. I was actually planning on getting down and dirty tomorrow :)
but yes, it could be the
Cliff Woolley wrote:
On Mon, 8 Dec 2003, Geoffrey Young wrote:
Use of bare to mean is deprecated at modules/include.t line 120.
which is probably new to 5.8.2.
Interesting. doesn't occur within include.t. So it happens within the
framework?
hmm, perhaps. I was actually planning
hi all
I've been thinking about this situation for a while now...
Original Message
Subject: FAIL Apache-Test-1.06 darwin 6.8
Date: Tue, 11 Nov 2003 01:03:19 +0200 (IST)
!!! no test server configured, please specify an httpd or apxs or put either
in your PATH. For example:
t/TEST
Mike Cramer wrote:
Geoffrey Young wrote:
I've tested it against everything I have. mike, if you can give CVS a
whirl today, that would be great.
I finally had a chance to try this out this morning and it worked
perfectly -- and when I forgot to feed it the path to apxs the first
time I tried
to specify the maximum number of seconds to wait for the test
server to start. the default is still 60 seconds. [Geoffrey Young]
use apxs PREFIX to resolve relative httpd.conf directives
ServerRoot is not present [Mike Cramer]
add support for a new subclass method 'bug_report', which if provided
this is in now.
I've tested it against everything I have. mike, if you can give CVS a whirl
today, that would be great.
$ cvs -z9 :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout
mod_perl-2.0
or
$ cvs -z9 :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout httpd-test
thanks.
--Geoff
Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
geoff 2003/11/07 07:03:39
Modified:perl-framework/Apache-Test/lib/Apache TestConfigParse.pm
Log:
use apxs PREFIX to resolve relative httpd.conf directives
ServerRoot is not present
Revision ChangesPath
1.36 +48 -6
actually, the 'errors' might not end up being errors at all - if the
configuration script can't resolve conf/mime.types, for instance, but
the EU has one in his t/conf directory everything should work out fine.
if that's the case, why not having A-T look in that directory and keep
things
101 - 200 of 268 matches
Mail list logo
