On Nov 8, 2004, at 8:23 PM, Geoffrey Young wrote:
a release candidate for Apache-Test 1.16 is now available.
All tests pass for me, both in Apache::Test and in my module that uses
it.
Regards,
David
On Oct 26, 2004, at 10:00 AM, Geoffrey Young wrote:
that's not so bad, but it will affect users somewhat - I know that I
have
used it in at least one of my tests...
Bleh. Bad Geoff!
maybe keeping $RedirectOK but moving the perl-framework (and mod_perl)
over
to the new API would be a nice
On Oct 25, 2004, at 4:33 PM, Geoffrey Young wrote:
let's give david a chance to investigate - either to fix or, if a
quick fix
isn't obvious, revert the behavior.
if david doesn't respond by, say, wednesday, we (you or I) should feel
free
to just revert the change. maybe david is on vacation
On Oct 19, 2004, at 2:48 PM, Stas Bekman wrote:
In which case, can you please review Boris' patch and commit it if you
think it's good? As I haven't coded and haven't used much this
feature, I'd rather let somebody who is more familiar with it do the
decision. If it breaks something, we can
the documentation to
this effect and commit the simple patch.
Regards,
David
--
David Wheeler
President, Kineticode, Inc.
http://www.kineticode.com/
Kineticode. Setting knowledge in motion.[sm]
On Oct 18, 2004, at 5:06 PM, [EMAIL PROTECTED] wrote:
add new test_config make target, equivalent to t/TEST -conf,
and make it a prerequisite for the cmodules make target. now
you can 'make cmodules' to build the things in c-modules/
without running t/TEST -conf first.
Uh, what? Can you
On Oct 18, 2004, at 4:52 PM, Boris Zentner wrote:
No, in that case I return $RedirectOK. I think that at least the
return 0 if $request-method eq 'POST';
line is wrong, since I clearly have no chance to redirect a post
request.
I just left it that way because that the way it was when I started
On Oct 19, 2004, at 5:22 AM, Stas Bekman wrote:
Is it because you can't really do redirects on real POST requests? The
body will get lost, isn't it?
No, we do them all the time in Bricolage.
Regards,
David
On Oct 18, 2004, at 3:43 AM, William Ross wrote:
Having replaced a powerbook, I've been banging my head against
libapreq again, o joy. I can confirm that in order to install it you
need to apply Stas's patch from last year, as found here:
On Oct 11, 2004, at 6:36 AM, Geoffrey Young wrote:
a release candidate for Apache-Test 1.14 is now available.
http://perl.apache.org/~geoff/Apache-Test-1.14-dev.tar.gz
All tests pass for me, and my module that uses Apache::TestMB continues
to work nicely with this version installed.
Thanks,
On Sep 10, 2004, at 3:00 PM, William McKee wrote:
I'm getting an error when trying to use Stas' template[1] with your
module. Basically, the filter_args() method is generating an error. I
am
calling it like this:
Apache::TestMB::filter_args();
You don't need to do that. Apache::TestMB does it
On Sep 11, 2004, at 10:19 AM, William McKee wrote:
I'm liking Module::Build more and more ;).
Me, too.
Scroll down a bit more to see the Build.PL example I added.
Oops, I hadn't realized that you updated that page after you released
Apache::TestMB. Thanks for your work on integrating M::B with
On Aug 19, 2004, at 12:17 PM, Stas Bekman wrote:
You can download the release candidate from here:
http://www.apache.org/~stas/Apache-Test-1.13-dev.tar.gz
All tests pass for me, and it appears to work nicely with my module
that uses Apache::TestMB.
Regards,
David
smime.p7s
Description: S/MIME
On Jul 30, 2004, at 6:30 AM, Boris Zentner wrote:
So I think if LWP is used, instead of passing requests_redirectable to
LWP,
the 1 should be changed to [ qw/GET POST HEAD/ ] or propably more.
This patch
passwd all my tests.
Yes, of course you're right. It has just been so long since I looked at
On Jul 31, 2004, at 1:14 AM, Stas Bekman wrote:
so, have_foo is intuitive to be used anywhere in the code, and plan
now will look like:
plan tests = 5, need_lwp, need_cgi, need_php;
I like this, but isn't it putting the onus of change on module owners
and introducing the likelihood of
On Jul 28, 2004, at 1:29 AM, Stas Bekman wrote:
Boris Zentner wrote:
Hi,
recently I try to use Apache::Test with HTTP::Cookies. But it did not
work as expected. I suppose the way to add a cookie_jar to A::T was
with 'Apache::TestRequest::user_agent'. I read the docs from
Why not use L for links in the docs?
--- src/docs/general/testing/testing.pod.~1.33.~ Sat May 1 16:53:19
2004
+++ src/docs/general/testing/testing.pod Fri Jul 16 10:36:15 2004
@@ -3167,7 +3167,7 @@
to test any web application from end to end based application as if it
were a black box
Hi All,
Still looking at the testing.pod, I see list items like this:
=over
=item * -order=rotate
rotate the tests: a, b, c, a, b, c
=item * -order=repeat
repeat the tests: a, a, b, b, c, c
=item * -order=random
run in the random order, e.g.: a, c, c, b, a, b
=back
I think that's generally
On Jul 16, 2004, at 10:46 AM, David Wheeler wrote:
Hi All,
Still looking at the testing.pod, I see list items like this:
Oops, wrong list for these questions. Apologies. Moving over to
docs-dev...
Regards,
David
On Jul 16, 2004, at 12:40 PM, Stas Bekman wrote:
Because it's not supported by Pod::POM and wasn't part of the
perlpodspec until recently. Pod::POM detects and auto-links http://
refs on its own, without needing L.
Okay.
David
smime.p7s
Description: S/MIME cryptographic signature
On Jul 16, 2004, at 12:48 PM, Stas Bekman wrote:
Without * it won't generate the bullets. I wanted the bullets so * is
there.
Okay.
David
smime.p7s
Description: S/MIME cryptographic signature
On Jul 14, 2004, at 5:01 PM, [EMAIL PROTECTED] wrote:
+If a directory t/lib exists from where the tests are run, adjust
[EMAIL PROTECTED] so that this directory is added when running the tests,
+both within t/TEST and within t/conf/modperl_inc.pl.
+This allows inclusion of modules specific
On Jul 7, 2004, at 7:01 AM, Geoffrey Young wrote:
the bug reporting skeleton has become so useful for me (and others)
that I
have created two new skeletons:
I would add a Build.PL with these contents:
use 5.00503;
use Apache::Test::MB;
Apache::Test::MB-new(
module_name =
On Jul 9, 2004, at 11:41 AM, Stas Bekman wrote:
Isn't that Apache::TestMB?
D'oh! Yes! Sorry!
use 5.00503;
use Apache::TestMB;
Apache::TestMB-new(
module_name = 'Apache::Test::Skeleton',
)-create_build_script;
And in fact, to make it more generally useful, I think I'd actually
make it:
use
On Jul 9, 2004, at 1:01 PM, Stas Bekman wrote:
I think we should try to be consistent with all TestM* frontends, no?
Yes.
I think we kept this message, in the same fashion to MakeMaker writing
what does it do. and it's good to tell the user that a utility was
created, so they know they can use
On Jul 9, 2004, at 1:09 PM, Stas Bekman wrote:
There is no Apache.pm in mp2. You probably wanted to say:
requires = { 'mod_perl' = 0,
Right. In fact, it should probably be
requires = { 'mod_perl' = '1.0',
in the MP1 example, and
requires = { 'mod_perl' =
On Jul 9, 2004, at 1:19 PM, Stas Bekman wrote:
It's up to you, since at the moment you are the only MB dev -- you are
the king :)
I'll leave it for now, then.
David
On Jul 9, 2004, at 1:38 PM, Stas Bekman wrote:
It won't work since the version number lives in the package mod_perl.
and most likely you'd want to require a minimal version at some point.
Ah, but this is one of the beauties of Module::Build, my friends.
Behold!
use 5.00503;
use Apache::TestMB;
On Jul 9, 2004, at 2:03 PM, Randy Kobes wrote:
But won't the CPAN indices (which are used by both CPAN.pm
and CPANPLUS.pm) still just recognize one version of
mod_perl.pm? Either the current one associated with mp1, or,
when mp2 is out of development, that associated with mp2
(assuming mod_perl.pm
On Jul 9, 2004, at 2:23 PM, Stas Bekman wrote:
I don't know how M::B does the version checking, but EU::MM does file
parsing, searching for the $VERSION line, so the version number must
be hardcoded there, unless you do something like:
$VERSION = do { require Apache2; require mod_perl.pm;
On Jul 6, 2004, at 12:56 AM, Stas Bekman wrote:
Committed, should there be a log in Changes?
Yep, thanks.
David
On Jul 5, 2004, at 9:01 AM, William McKee wrote:
Actually I'd prefer the following format:
my $build = $build_pkg-new (...);
$build-create_build_script;
The reason is that this shows how to work with a build object. This is
necessary if you want to use methods such as generate_script.
Yeah, I
On Jul 5, 2004, at 11:53 AM, William McKee wrote:
OK, that worked. Why is it named differently from the format used by
Apache::TestMM? Nevermind, I see your follow-up message. That works for
me!
Probably do to some overly-aggressive find and replace or something.
Sorry about that!
David
On Jul 2, 2004, at 9:19 AM, William McKee wrote:
Thanks for your efforts in adding support
Glad it works for you!
This reminds me:
--- Test.pm.~1.84.~ Fri Jun 25 18:55:53 2004
+++ Test.pm Fri Jul 2 09:27:18 2004
@@ -807,7 +807,8 @@
exports a number of useful functions for sending request to the
On Jul 2, 2004, at 9:34 AM, William McKee wrote:
Hi all,
Sorry about that false start. Lemme try this again! As I was saying,
David, thanks for adding support for Module::Build. I'm trying to
replace one of my existing projects using the Apache::TestMB module. It
works fine unless I try to do
On Jun 27, 2004, at 1:21 PM, Stas Bekman wrote:
Heh, sorry. Should have been easily do-able with patch -p1, though.
Ah, right, too many flags to remember :) it's easier when all patches
are in the same format :)
Yeah, -p is the only one I actually know, since I often get patches
generated from
On Jun 28, 2004, at 6:14 AM, Geoffrey Young wrote:
that's ok - I have rerolled a new candidate with these changes
incorporated
for you to test ;)
if all looks good to you I'll release.
All tests pass for me. I don't know if this was intentional, but the
new tests I introduced last week aren't
with
request callback order of execution.
- Fixed failing tests of notes functionality under Apache. Not
sure
how they ever passed, frankly.
Enjoy!
David
Begin forwarded message:
From: PAUSE [EMAIL PROTECTED]
Date: June 28, 2004 10:07:00 AM PDT
To: David Wheeler [EMAIL PROTECTED]
Subject: CPAN
On Jun 28, 2004, at 12:39 PM, Stas Bekman wrote:
Thanks, committed. David, in the future please create patches with
'cvs diff' so that they can be applied easily, thanks :)
Heh, sorry. Should have been easily do-able with patch -p1, though.
Regards,
David
On Jun 25, 2004, at 4:49 PM, David Wheeler wrote:
Hrm, nope. I just installed the latest on another box and the
redirection still works properly. Odd...
So let's introduce some tests to see where it happens, hrm??
diff -Naur old/t/conf/extra.conf.in new/t/conf/extra.conf.in
--- old/t/conf
On Jun 25, 2004, at 8:23 AM, Geoffrey Young wrote:
nope. I think apache.org has been having email issues - my announce
came 3
hours later, and a bunch of messages were duplicated. or maybe it was
just me.
No, I'm on the road and just found out that the network I'm on has
sendmail stuff locked
On Jun 25, 2004, at 12:02 PM, Geoffrey Young wrote:
check the version of lwp - IIRC there was a behavior change in recent
versions.
You could be right. I have the latest, 5.79, on that box, and 5.76 on
my other boxes. Seems like it might make sense to fix that before
releasing 1.12. I'll look
On Jun 25, 2004, at 1:49 PM, David Wheeler wrote:
You could be right. I have the latest, 5.79, on that box, and 5.76 on
my other boxes. Seems like it might make sense to fix that before
releasing 1.12. I'll look at it later today if you don't beat me to
it. It'll be tomorrow at the soonest I
On Jun 23, 2004, at 1:26 PM, Geoffrey Young wrote:
sure, I'll try to wrap up a candidate tomorrow.
Sweet, thanks!
David
On Jun 23, 2004, at 10: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.
Here's a quick documentation patch, essentially, for the unimplemented
cmodules actions:
--- lib/Apache/TestMB.pm.~1.1.~ Wed Jun 23 09:51:15
On Jun 22, 2004, at 3:34 PM, David Wheeler wrote:
I doubt so. Just make it die with the appropriate message, so that if
someone needs it they will know that it'll be added in the future.
Okay, done.
Uh, and here it is.
Regards,
David
Hi All,
Here's a new subclass for Module::Build, Apache::TestMB, which allows
modules that use Module::Build to run tests using Apache::Test. My
assumption is that it would be distributed with Apache::Test; therefore
its use is something like this:
use Module::Build;
my $build_pkg = eval {
On Jun 21, 2004, at 8:29 PM, Ken Williams wrote:
I see - so the author would design their tests so they could be run
either with or without a live server? I'm guessing many authors would
want to require a live server, and thus rely on Apache::TestMB.
Most module authors design their tests to
On Jun 21, 2004, at 6:12 PM, David Wheeler wrote:
Here's a new subclass for Module::Build, Apache::TestMB, which allows
modules that use Module::Build to run tests using Apache::Test.
Let me make a few comments on my XXX comments in the source code, and
aske a couple of questions
On Jun 22, 2004, at 6:23 AM, Ken Williams wrote:
./Build help should work already. ./Build help $newaction should work
automatically if you add documentation for each action - it searches
for docs using the regex /^=item\s+\Q$action\E\b/ .
Ah, I had =item Caction. I'll remove the C.
Thanks,
On Jun 22, 2004, at 7:32 AM, Randy Kobes wrote:
Right now the Makefile is generated by methods within
Apache/TestConfigC.pm, which generally consists of calling
the apxs utility to compile the module (as well as
implementing a 'clean' target). In principle I think this
could be done via
On Jun 22, 2004, at 10:33 AM, Stas Bekman wrote:
Absolutely. It's really just:
MyTest-new-run(@ARGV);
where MyTest is a subclass of Apache::TestRunPerl
I tried that, but it didn't work. I'm not sure why. The first problem
was this code:
$0 = File::Spec-rel2abs($0);
if (-e $0) {
Oops, sorry for the dupe.
David
On Jun 22, 2004, at 12:19 PM, Randy Kobes wrote:
Sure, it should be relatively straightforward ... But I'd
like to get, especially, Stas' opinion on this - adding this
in will necessarily introduce a few branches in the
Apache/TestConfigC.pm code related to, first of all, whether
to write a
On Jun 22, 2004, at 2:44 PM, Stas Bekman wrote:
It may be a fairly complex logic to add, though you could write
wrappers that simply push things into @ARGV, emulating the command
line.
Though I'd rather have one way to do things. It's already a
non-trivial thing with all the multiple options.
On Jun 22, 2004, at 3:15 PM, Stas Bekman wrote:
Yes, but it won't work for modules not using MB, so it's better to
have something common. We can always change things later if we find it
beneficial. Nothing is cast in stone as long as it doesn't add a huge
overhead for the user's learning curve.
On Jun 14, 2004, at 1:40 PM, Stas Bekman wrote:
I suppose we could fix Apache::testold (it was renamed) to have -d if
it can be made into more than a hack. Though I'm not sure when a new
version of mp1 is going to be released.
Looks like it would be pretty easy to add to MM_test(), though I
On Jun 14, 2004, at 1:24 AM, Stas Bekman wrote:
A-T writes what it does:
Right, so does A-t:
/Users/david/dev/perl/mason-1.2/dist/t/httpd -f
/Users/david/dev/perl/mason-1.2/dist/t/httpd.conf
With Apache 1.x, A-T does this:
/usr/local/apache/bin/httpd -d
On Jun 14, 2004, at 10:30 AM, David Wheeler wrote:
So this is what I needed to know; thanks. I'll try to hack the Apache
startup code in this module to use -d and see if that helps things.
I was able to hack it in, but unfortunately it doesn't eliminate the
problem. Very odd...
Regards,
David
On Jun 14, 2004, at 10:37 AM, David Wheeler wrote:
I was able to hack it in, but unfortunately it doesn't eliminate the
problem. Very odd...
No, I take it back; it _did_ help! I just got a different error:
Ouch! ap_mm_create(1048576,
/Users/david/dev/perl/mason-1.2/dist/t/logs/httpd.mm.8917
On Jun 13, 2004, at 2:13 PM, Stas Bekman wrote:
I suppose so. Check that A-t generates ServerRoot setting
pointing to the local dir.
It does. I don't know what else might be the problem...what command
does A-T use to start Apache? Could it be different somehow than what
A-t uses?
Regards,
Hi All,
I'm working on a module in another project that's still using the old
Apache::test (not the lc test). When I attempt to use it with my copy
of apache with mod_ssl statically compiled in with mm support, I get
this error:
Ouch! ap_mm_create(1048576, /usr/local/apache/logs/httpd.mm.6521)
On May 19, 2004, at 9:02 PM, Geoffrey Young wrote:
a release candidate for Apache-Test 1.11 is now available.
http://perl.apache.org/~geoff/Apache-Test-1.11-dev.tar.gz
please take the time to excercise the candidate through all your
existing
applications that use Apache-Test and report back
On Apr 16, 2004, at 2:05 PM, Stas Bekman wrote:
A few problems were noticed and fixed, thanks to Ken Coar. So here is
a new RC. Same URL:
All tests still pass for me, including in my module.
Regards,
David
On Apr 16, 2004, at 2:05 PM, Stas Bekman wrote:
A few problems were noticed and fixed, thanks to Ken Coar. So here is
a new RC. Same URL:
All tests still pass for me, including in my module.
Regards,
David
--
Report problems: http://perl.apache.org/bugs/
Mail list info:
On Apr 15, 2004, at 12:26 PM, Stas Bekman wrote:
Unless someone reports problems, I'm going to release a new version of
Apache-Test tomorrow. Please test this release candidate:
http://perl.apache.org/~stas/Apache-Test-1.10-dev.tar.gz
All tests pass for me, and my module that uses it still
On Mar 24, 2004, at 11:39 AM, Stas Bekman wrote:
David, as usual you are more than welcome to submit a patch that
explains things. That'd be the Apache::TestMM manpage.
Here you go. My mailer will likely screw up the line endings, so I've
also attached it so that you'll get it, Stas.
---
On Mar 24, 2004, at 11:36 AM, Geoffrey Young wrote:
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
On Mar 25, 2004, at 11:31 AM, Stas Bekman wrote:
I think these belong to the Apache::TestConfig manpage, since that's
where they come from in code. If we document those here, we won't
remember to update the doc. So I think adding them to
Apache::TestConfig and cross-referencing from here to
On Mar 25, 2004, at 12:08 PM, Stas Bekman wrote:
Hmm, thinking some more, may be we could just suggest to look in
Apache::TestConfig::Usage or the output of t/TEST -h? that probably
won't do, right? the reason I hesitate is the duplication of the
information, which eventually will end up being
On Mar 25, 2004, at 12:17 PM, Stas Bekman wrote:
Good point. How about:
To see the available options and their meaning run:
perl -MApache::TestConfig -le 'Apache::TestConfig::usage()'
Bleh. How 'bout if filter_args() can watch for -help and do this for
you? Then people can just:
perl
On Mar 25, 2004, at 1:12 PM, Stas Bekman wrote:
That doesn't sound very intutitive to me. I suggest the following
happy compromise:
Document a few of the most commonly wanted config args
(-httpd/-apxs/...) and add the command how to get the rest, by calling
usage().
Sure, okay.
Regards,
David
Are all of the options parsed by Apache::TestMM::filter_args()
documented somewhere?
Thanks,
David
On Mar 4, 2004, at 4:15 PM, Stas Bekman wrote:
The patch below attempts to give users an idea to try before they rush
to report a bug. For example:
waiting 120 seconds for server to start: not ok
giving up after 121 secs. If you think that your system
is slow or overloaded try again with a
On Mar 4, 2004, at 5:09 PM, Stas Bekman wrote:
Not in this case. T-H wasn't called yet. It gets called only after
server successfully starts.
Ah, right, okay.
If you they did:
% make test
but you'd suggest to run:
% ./Build test
not only it'll confuse the user, who aren't aware of Build or t/TEST
On Feb 23, 2004, at 4:53 PM, 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
Thanks.
All tests
On Jan 30, 2004, at 5:18 PM, Stas Bekman wrote:
David, I've committed the required changed. Please test that it works
for you.
I still have a few other things to fix (t/SMOKE), but they shouldn't
affect you.
Yep, works great for me. Thanks!
David
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};
Surely you mean
my $serverroot = Apache::Test::config()-{vars}-{serverroot};
although this should work, too:
my $serverroot =
On Jan 23, 2004, at 8:27 AM, Geoffrey Young wrote:
it's not that I don't agree this ought to be fixed, or that with the
patch
we have desirable behavior, it's just that I want it to be easy and the
current ServerRoot placement isn't really easy or intuitive. maybe
Apache::Test could export a
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,
Apache::Test-serverroot
That's kind of cool.
David
Hi All,
A while ago, I enquired about the Cwd that Apache::Test uses, and asked
if something could be added to make it different. This is because a lot
of existing test modules (such as Test::POD) expect tests to be run
from the distribution package root. Apache::Test is fairly unique
(outside
On Jan 20, 2004, at 11:20 PM, Stas Bekman wrote:
Does the patch below solve the problem?
Maybe, but it's not quite there yet:
Can't locate object method chdir_t via package Apache::TestHarness
at lib/Apache/TestRun.pm line 648.
Not yet. It should be trivial for someone who knows Module::Build,
On Jan 21, 2004, at 12:39 PM, Stas Bekman wrote:
Sorry, David, I guess I was testing with the wrong version. Here is a
new patch. It breaks quite a few tests in modperl-2.0 but it's because
they rely on that chdir_t, and can be fixed to be relocatable. It's
possible that there are other
On Jan 21, 2004, at 1:11 PM, Stas Bekman wrote:
It just doesn't do any chdirs, so you can really run:
/foo/bar/tar/mar/t/TEST and it will run from /
Cool, I suspect that that's more or less how Test::Harness works, too
-- it just runs the test from whatever Cwd you're in when you call
On Jan 21, 2004, at 2:03 PM, Stas Bekman wrote:
So does it all just work or you haven't had a chance to test my rework
of the sticky configuration? Once you are happy with it, I'd like to
invite more testers from the outside (probably post to modperl users
list) before we make a new A-T
On Jan 21, 2004, at 2:00 PM, Stas Bekman wrote:
I think, yes.
It's actually a goodness to make tests relocatable, in case someone
moves things around.
Nice.
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
On Jan 21, 2004, at 3:15 PM, Stas Bekman wrote:
So did you get the interactive prompt for the first time? (which of
course shouldn't happen if you have passed the -httpd/-apxs args/or if
it was against mp2, which it then has used and will remember to use in
the future if you don't pass any
a documentation update. Patch attached.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL
list software strips them off! I'll send it to
you directly.
Must've been a change in LWP or something.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo
for me.
Daviid
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting
and report back any
problems.
I think that this release contains my fixes to the TestRequest::POST
documentation, too. Or was that in 1.04?
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com
stuff like that was always noted.
Cheers,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting knowledge
you get the username and group from httpd.conf? Couldn't use
use that information to do chown and chgrp?
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://kineticode.com/ Yahoo!: dew7e
group of people who can run tests.
I think a better idea is to introduce a test function like have_lwp,
maybe called has_access_to_t, that can be used by the module
developer to skip the relevant tests, if necessary.
Regards,
David
--
David Wheeler AIM: dwTheory
': $!\n;
?
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting
/Peek/Peek.bundle
definition of _DeadCode
/Users/david/.cpanplus/5.8.0/build/Apache-Peek-1.01/blib/arch/auto/
Apache/Peek/Peek.bundle definition of _DeadCode
mercury%
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
today.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode
for the test scripts as they are run, that should be
documented, as it varies from what the module author usually expects --
including from the behavior of the old Apache::test.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED
/arch/auto/
Apache/Peek/Peek.bundle definition of _DeadCode
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://kineticode.com/ Yahoo!: dew7e
1 - 100 of 132 matches
Mail list logo
