Re: resolving Apache::Test vs. Apache::test collision

2003-06-19 Thread Stas Bekman
David Wheeler wrote: On Wednesday, June 18, 2003, at 07:30 AM, Stas Bekman wrote: Now just awaiting a confirmation from David and I'll put Apache::Test 1.03 on CPAN. David, if you see this before tomorrow, simpy try the latest cvs, I have already committed the needed change. Hopefully it does

Re: resolving Apache::Test vs. Apache::test collision

2003-06-18 Thread Randy Kobes
On Tue, 17 Jun 2003, Stas Bekman wrote: [ .. ] David, please test this patch. This version performs the cleanup only during 'make install'. what I'm not sure about is whether it handles correctly some weird paths when creating the packlist. I think it should work, since nothing is passed via

Re: resolving Apache::Test vs. Apache::test collision

2003-06-18 Thread Stas Bekman
Now just awaiting a confirmation from David and I'll put Apache::Test 1.03 on CPAN. David, if you see this before tomorrow, simpy try the latest cvs, I have already committed the needed change. Hopefully it does do the right thing for you.

Re: resolving Apache::Test vs. Apache::test collision

2003-06-18 Thread David Wheeler
On Wednesday, June 18, 2003, at 07:30 AM, Stas Bekman wrote: Now just awaiting a confirmation from David and I'll put Apache::Test 1.03 on CPAN. David, if you see this before tomorrow, simpy try the latest cvs, I have already committed the needed change. Hopefully it does do the right thing

Re: resolving Apache::Test vs. Apache::test collision

2003-06-17 Thread Stas Bekman
David Wheeler wrote: On Monday, June 16, 2003, at 02:42 AM, Stas Bekman wrote: OK, here is the patch that nukes Apache/test.pm. Please test it on case-insensitive systems (if you don't have Apache/test.pm, please add it just to test). Once you confirm that it works, I release Apache::Test

Re: resolving Apache::Test vs. Apache::test collision

2003-06-17 Thread David Wheeler
On Monday, June 16, 2003, at 08:02 PM, Stas Bekman wrote: Any idea why has it failed to delete the file? I've copied the code from forceunlink sub in MakeMaker (which is called on UNINST=1), it changes the mode to 0666 and then attempts to delete the file. Because I ran it as a non-root user.

Re: resolving Apache::Test vs. Apache::test collision

2003-06-17 Thread Stas Bekman
Stas Bekman wrote: David Wheeler wrote: On Monday, June 16, 2003, at 08:02 PM, Stas Bekman wrote: Any idea why has it failed to delete the file? I've copied the code from forceunlink sub in MakeMaker (which is called on UNINST=1), it changes the mode to 0666 and then attempts to delete the

Re: resolving Apache::Test vs. Apache::test collision

2003-06-16 Thread Stas Bekman
OK, here is the patch that nukes Apache/test.pm. Please test it on case-insensitive systems (if you don't have Apache/test.pm, please add it just to test). Once you confirm that it works, I release Apache::Test 1.03, so we can go ahead with the new libapreq release. Index: Changes

Re: resolving Apache::Test vs. Apache::test collision

2003-06-16 Thread David Wheeler
On Monday, June 16, 2003, at 02:42 AM, Stas Bekman wrote: OK, here is the patch that nukes Apache/test.pm. Please test it on case-insensitive systems (if you don't have Apache/test.pm, please add it just to test). Once you confirm that it works, I release Apache::Test 1.03, so we can go ahead

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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?).

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread Philippe M. Chiasson
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread David Wheeler
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-28 Thread James G Smith
---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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-23 Thread Stas Bekman
Randy Kobes wrote: On Thu, 22 May 2003, Randy Kobes wrote: On Thu, 22 May 2003, Stas Bekman wrote: [ ... ] It'd be very helpful if somebody could do a bit of processing of CPAN and figure who uses Apache::test and compile a list of their email addresses. Here's a list of packages that have

Re: resolving Apache::Test vs. Apache::test collision

2003-05-22 Thread Randy Kobes
On Thu, 22 May 2003, Stas Bekman wrote: [ ... ] So is everybody happy with this solution? (rename Apache/test.pm with Apache/testold.pm). So we can give Geoff a green light to publish his article? Sounds good ... It'd be very helpful if somebody could do a bit of processing of CPAN and

Re: resolving Apache::Test vs. Apache::test collision

2003-05-22 Thread Randy Kobes
On Thu, 22 May 2003, Randy Kobes wrote: On Thu, 22 May 2003, Stas Bekman wrote: [ ... ] It'd be very helpful if somebody could do a bit of processing of CPAN and figure who uses Apache::test and compile a list of their email addresses. Here's a list of packages that have Apache::test

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
David Wheeler wrote: On Tuesday, May 13, 2003, at 09:11 PM, Stas Bekman wrote: so that bug should be fixed in CPANPLUS, in any case new Apache/test will have a $VERSION Yes. I sent them a patch. We'll see if they apply it. So we probably should check whether UNINST=1 is on, and if not (and if

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
David Wheeler wrote: 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?). So it doesn't matter which one gets overwritten. Give it a try. But you can't have

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
David Wheeler wrote: 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 appears to work,

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
David Wheeler wrote: 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 simplest. Sounds okay

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
David Wheeler wrote: On Monday, May 19, 2003, at 07:18 PM, Stas Bekman wrote: my $is_case_insensitive = -e catfile qw(lib Apache test.pm); Ah, yes, of course. So there _is_ a simple way to test for it! if it works, then yes! It works: % perl -e 'print -e lib/Apache/test.pm ? insensitive\n :

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
Moreover, since now we know how to test for case-insensitive fs, we can copy Apache/testold.pm to Apache/test.pm on case-sensitive platforms which singles OSX as the only potentially problematic platform and only for 3rd party modules, which will be encouraged to rename

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
The only problem is with those 1.x 3rd party modules, but they will updated to 'require Apache::testold', which we can distribute in Apache-Test. Ah, but as I said, if they have Apache::test in their distros (as in fact does MasonX::ApacheHandler::WithCallbacks and, IIRC, HTML::Mason), it

Re: resolving Apache::Test vs. Apache::test collision

2003-05-20 Thread Stas Bekman
David Wheeler wrote: On Monday, May 19, 2003, at 07:57 PM, Stas Bekman wrote: As long as they hide it from MakeMaker so it won't attempt to install it, which will just cause an inconvenience to its users. Of course. Mine is in t/lib, as is Mason's, I believe. And here is a patch that will try

Re: resolving Apache::Test vs. Apache::test collision

2003-05-16 Thread Stas Bekman
Folks please send your feedback on this last proposal, so we can close this issue asap. In case you have missed it: http://marc.theaimsgroup.com/?l=apache-test-devm=105288551432493w=2 __ Stas BekmanJAm_pH -- Just

Re: resolving Apache::Test vs. Apache::test collision

2003-05-16 Thread Geoffrey Young
Stas Bekman wrote: Folks please send your feedback on this last proposal, so we can close this issue asap. In case you have missed it: http://marc.theaimsgroup.com/?l=apache-test-devm=105288551432493w=2 the solution seems reasonable to me, but then again I never had a problem :) from what I

Re: resolving Apache::Test vs. Apache::test collision

2003-05-16 Thread Randy Kobes
On Fri, 16 May 2003, Geoffrey Young wrote: Stas Bekman wrote: Folks please send your feedback on this last proposal, so we can close this issue asap. In case you have missed it: http://marc.theaimsgroup.com/?l=apache-test-devm=105288551432493w=2 the solution seems reasonable to

Re: resolving Apache::Test vs. Apache::test collision

2003-05-14 Thread Stas Bekman
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 few subs that are not. May be this other functionality should move elsewhere. given that almost all of the functions from the various Test*

Re: resolving Apache::Test vs. Apache::test collision

2003-05-14 Thread Stas Bekman
David Wheeler wrote: 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 Apache::Test to

Re: resolving Apache::Test vs. Apache::test collision

2003-05-14 Thread Geoffrey Young
Unfortunately this solution won't work. If you have PREREQ_PM = {Apache::Test = 1.03}, MakeMaker is going to 'require Apache::Test' and either won't find it or will find Apache::test on case-insensitive platforms. What a bummer. yes, I thought about that already as I began to revamp my

Re: resolving Apache::Test vs. Apache::test collision

2003-05-14 Thread Stas Bekman
Geoffrey Young wrote: Unfortunately this solution won't work. If you have PREREQ_PM = {Apache::Test = 1.03}, MakeMaker is going to 'require Apache::Test' and either won't find it or will find Apache::test on case-insensitive platforms. What a bummer. yes, I thought about that already as I

Re: resolving Apache::Test vs. Apache::test collision

2003-05-13 Thread Stas Bekman
David Wheeler wrote: 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 Apache::Test to

Re: resolving Apache::Test vs. Apache::test collision

2003-05-12 Thread Geoffrey Young
I actually like Apache::TestPlan, it's most of the functionality that this module provides. but there are a few subs that are not. May be this other functionality should move elsewhere. given that almost all of the functions from the various Test* packages are exported by default and almost

Re: resolving Apache::Test vs. Apache::test collision

2003-05-09 Thread Stas Bekman
Geoffrey Young wrote: So it seems to me that the simplest route to take is to s/Apache::Test/Apache::Tester/ as suggested by David. Only one file is modified. If there are no objections, I'll proceed with this route. not to be nitpicky, but Apache::Tester strikes me as, well, something. this

Re: resolving Apache::Test vs. Apache::test collision

2003-05-09 Thread Stas Bekman
Randy Kobes wrote: On Thu, 8 May 2003, Stas Bekman wrote: The problem with providing a replacement for Apache::test is that some people are going to reinstall older mod_perl versions and kill the overriden file. That's certainly true in general (for case-preserving but otherwise

Re: resolving Apache::Test vs. Apache::test collision

2003-05-09 Thread Stas Bekman
Randy Kobes wrote: On Thu, 8 May 2003, Stas Bekman wrote: [ .. ] One question remains: should the package be renamed to Apache-Tester as well? Since people will see Apache::Test and will try to install Apache::Test in CPAN.pm, and that won't work. Probably to make a clean break the whole package

Re: resolving Apache::Test vs. Apache::test collision

2003-05-09 Thread Geoffrey Young
So currently we are down to two options: 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. if you mean future versions of mp1, that's a good idea. that's probably

Re: resolving Apache::Test vs. Apache::test collision

2003-05-08 Thread Stas Bekman
Randy Kobes wrote: 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

resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Stas Bekman
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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Geoffrey Young
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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Stas Bekman
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.

Re: resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Stas Bekman
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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Stas Bekman
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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Stas Bekman
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

Re: resolving Apache::Test vs. Apache::test collision

2003-05-06 Thread Randy Kobes
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