OK, I'm a programmer, not a writer. Be gentle.
Nothing major, just the a mention of cookie_jar and additional headers
via the second param in GET (and probably others?).
While I was at it, I made sure all of the need* examples were all the
same; which meant removing \& and &. The bare versions s
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.,
t/modules/
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, 2
Christopher H. Laco wrote:
OK, I'm a programmer, not a writer. Be gentle.
Nothing major, just the a mention of cookie_jar and additional headers
via the second param in GET (and probably others?).
While I was at it, I made sure all of the need* examples were all the
same; which meant removing \&
Stas Bekman wrote:
Christopher H. Laco wrote:
OK, I'm a programmer, not a writer. Be gentle.
Nothing major, just the a mention of cookie_jar and additional headers
via the second param in GET (and probably others?).
While I was at it, I made sure all of the need* examples were all the
same; whic
Christopher H. Laco wrote:
Stas Bekman wrote:
Christopher H. Laco wrote:
OK, I'm a programmer, not a writer. Be gentle.
Nothing major, just the a mention of cookie_jar and additional
headers via the second param in GET (and probably others?).
While I was at it, I made sure all of the need* exampl
Stas Bekman wrote:
No, no, the root of A-T. An example will be more useful:
--- lib/Apache/Test.pm(revision 109410)
+++ lib/Apache/Test.pm(working copy)
I can chdir into the root of the project and apply your patch immediately.
Understood. Makes sense.
Agreed, but dups are evil from the mai
Christopher H. Laco wrote:
On that note, what else can I work on?
Apparently I'm a glutton for punishment.
Not sure, there are all kind of things in the ToDo file, but they all
mostly obscure.
I think all kind of refactoring would be great. One thing I wanted to do
for tests again vhosts, is to
I know we tried to avoid external dependencies, but Cwd coming with 5.6.x
is unusable under -T. At the moment this breaks some mp2 tests (the
problem comes from A-T, which indirectly invokes Cwd::cwd via File::Spec's
rel2abs. I've tried to code a workaround, but it doesn't work and it's a
bad i
Stas Bekman wrote:
I know we tried to avoid external dependencies, but Cwd coming with
5.6.x is unusable under -T. At the moment this breaks some mp2 tests
(the problem comes from A-T, which indirectly invokes Cwd::cwd via
File::Spec's rel2abs. I've tried to code a workaround, but it doesn't
wo
Stas Bekman wrote:
> Stas Bekman wrote:
>
>> I know we tried to avoid external dependencies, but Cwd coming with
>> 5.6.x is unusable under -T. At the moment this breaks some mp2 tests
>> (the problem comes from A-T, which indirectly invokes Cwd::cwd via
>> File::Spec's rel2abs. I've tried to co
Stas Bekman wrote:
Christopher H. Laco wrote:
On that note, what else can I work on?
Apparently I'm a glutton for punishment.
Not sure, there are all kind of things in the ToDo file, but they all
mostly obscure.
I think all kind of refactoring would be great. One thing I wanted to do
for tests
Geoffrey Young wrote:
Stas Bekman wrote:
Stas Bekman wrote:
I know we tried to avoid external dependencies, but Cwd coming with
5.6.x is unusable under -T. At the moment this breaks some mp2 tests
(the problem comes from A-T, which indirectly invokes Cwd::cwd via
File::Spec's rel2abs. I've tried t
Christopher H. Laco wrote:
Stas Bekman wrote:
Christopher H. Laco wrote:
On that note, what else can I work on?
Apparently I'm a glutton for punishment.
Not sure, there are all kind of things in the ToDo file, but they all
mostly obscure.
I think all kind of refactoring would be great. One thing
Stas Bekman wrote:
Still someone needs to do the work and verify that things are working.
That will fun in and of itself. Right now, the only thing close to
meeting the requirements of running the overall tests is my 5.6.1
install on my XP lappy. Both of my FreeBSD boxen are still 5.005_03.
It'l
Stas Bekman wrote:
I think all kind of refactoring would be great. One thing I wanted to
do for tests again vhosts, is to add this function next to
module2path():
sub module2url {
my $module = shift;
my $scheme = shift || "http";
Apache::TestRequest::module($module);
my $co
Of of course, I meant t/modperl/merge.t and module2url
Got perl on the brain.
After another look at things like t/merge.t, it looks like there are at
least 2 different use cases for module2perl.
1) The $module sent to module2perl will be sent to ::module() and will
be the same as the path. This
Christopher H. Laco wrote:
Stas Bekman wrote:
I think all kind of refactoring would be great. One thing I wanted
to do for tests again vhosts, is to add this function next to
module2path():
sub module2url {
my $module = shift;
my $scheme = shift || "http";
Apache::TestRequest::m
Stas Bekman wrote:
> Of course it should take the necessary precautions for when / is and
> isn't included, etc.
What do you mean? Examples?
Well, let's go with the running sample:
sub module2url {
my $module = shift;
my $scheme = shift || "http";
Apache::TestRequest::module($mod
Christopher H. Laco wrote:
Stas Bekman wrote:
> Of course it should take the necessary precautions for when / is and
> isn't included, etc.
What do you mean? Examples?
Well, let's go with the running sample:
sub module2url {
my $module = shift;
my $scheme = shift || "http";
Apach
Christopher H. Laco wrote:
Stas Bekman wrote:
Still someone needs to do the work and verify that things are working.
That will fun in and of itself. Right now, the only thing close to
meeting the requirements of running the overall tests is my 5.6.1
install on my XP lappy. Both of my FreeBSD box
21 matches
Mail list logo
