---BeginMessage---
-- justin ]
On Monday, May 19, 2003, at 06:41 PM, Stas Bekman wrote:
So we need to figure out how to enforce UNINST the old Apache/test.pm
if any.
For example we could adjust MY::install to unlink it, without messing
with UNINST=1, though the latter will be the
---BeginMessage---
-- justin ]
On Monday, May 19, 2003, at 05:08 PM, Stas Bekman wrote:
That's right. Let's try this next: I've attached a new patch, which
moves the creation of lib/Apache/test.pm into a Makefile.PL. On
case-insensitive systems it'll overwrite lib/Apache/Test.pm.
That
---BeginMessage---
[ This message is resent on behalf of David Wheeler [EMAIL PROTECTED].
-- justin ]
On Monday, May 19, 2003, at 03:43 PM, Stas Bekman wrote:
That's the trick. Each of these files contains both Apache::test and
Apache::Test (do you see that each has require() called twice?).
---BeginMessage---
[ This message is resent on behalf of David Wheeler [EMAIL PROTECTED].
-- justin ]
On Tuesday, May 13, 2003, at 08:08 PM, Stas Bekman wrote:
If an old mod_perl 1.0 is installed and it overrides Apache::Test,
Makefile.PL will simply fail to satisfy the requirement of a
---BeginMessage---
-- justin ]
On Thursday, May 8, 2003, at 05:44 PM, Stas Bekman wrote:
1) Integrate test.pm in Test.pm. I think we should bundle Apache::Test
with future versions of mod_perl to make the maintenance simple and
remove the original Apache::test from it.
2) Rename
---BeginMessage---
[ This message is resent on behalf of Philippe M. Chiasson
[EMAIL PROTECTED]. -- justin ]
On Tue, 2003-05-13 at 07:36, Stas Bekman wrote:
Geoffrey Young wrote:
I actually like Apache::TestPlan, it's most of the functionality that
this module provides. but there are a
---BeginMessage---
[ This message is resent on behalf of Jeremy Brown [EMAIL PROTECTED].
-- justin ]
Hi,
I found it pretty hard to configure flood with current documentation. I
found some good examples with the package but nothing really covering
conglomerates and other types of advanced setups.
---BeginMessage---
-- justin ]
On Tuesday, May 6, 2003, at 10:40 AM, Randy Kobes wrote:
I'm beginning to think that, for all the up-front hassle of it,
just renaming it to Apache::Tester or Test::Apache will avoid
more headaches in the long run.
That's a good point, although as Stas
---BeginMessage---
[ This message is resent on behalf of David Wheeler [EMAIL PROTECTED].
-- justin ]
On Monday, May 5, 2003, at 07:34 PM, Stas Bekman wrote:
I don't think this will be robust enough, since vendors tend to do
things in their own subtle ways. It's probably much better to
---BeginMessage---
[ This message is resent on behalf of James G Smith [EMAIL PROTECTED].
-- justin ]
Stas Bekman [EMAIL PROTECTED] wrote:
We have a problem with using the Apache::Test name, more correctly we have a
problem with using the Apache/Test.pm filename. On platforms with
On Tue, 27 May 2003 18:10:47 -0700
Jeremy Brown [EMAIL PROTECTED] wrote:
[...]
I found it pretty hard to configure flood with current documentation. I
found some good examples with the package but nothing really covering
conglomerates and other types of advanced setups.
That might be just
11 matches
Mail list logo
