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
case-insentive filesystems (winFU, Mac OS X) if mod_perl 1.x is installed,
there is Apache/test.pm (notice the lower case 't'). So when you say 'use
Stas Bekman 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
case-insentive filesystems (winFU, Mac OS X) if mod_perl 1.x is
installed, there is Apache/test.pm (notice the lower case 't'). So
I can see a third possibility - installing Apache::Test relative to
Apache2, that way there is no namespace collision and uses can control
their destiny.
This is not an option. Apache::Test should be available unrelated to
availability of mp2.
David Wheeler wrote:
On Monday, May 5, 2003, at 05:19 PM, Geoffrey Young wrote:
ok, so it's not like that I don't believe that this is an issue, but I
don't believe you - if you have Apache/test.pm and you install 2.0
then Apache/Test.pm would replace the existing file, no? that's why
Apache2
David Wheeler wrote:
On Monday, May 5, 2003, at 06:13 PM, Joe Schaefer wrote:
Seems like a workable compromise to me: if all we have to do is
s/Apache::Test/Test::Apache/ for libapreq-1.x, that seems easy
enough.
You know, we might be able to eliminate this whole problem by having
Apache::Test
David Wheeler wrote:
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
explicitly search @INC, rather than relying on INSTALLVENDORARCH.
Hrm, yes, I guess
On Tue, 6 May 2003, David Wheeler wrote:
On Tuesday, May 6, 2003, at 08:49 AM, Randy Kobes wrote:
An upshot of this is that, when installing Apache-Test,
a system file Apache/Test.pm or Apache/test.pm should
probably be unlinked before copying to the blib/ directory.
Yes, and hope
