perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Wheeler <>
Subject Re: resolving Apache::Test vs. Apache::test collision
Date Mon, 19 May 2003 22:49:36 GMT
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 them both in the tarball, because users will get an 
error when they unpack them and will send you bug reports. Here's what 
happens when I apply the patch, just to give you an idea.

mercury% patch -p0 < ~/Desktop/patch      The next patch would create 
the file Apache-Test/lib/Apache/,
which already exists!  Assume -R? [n]
Apply anyway? [n] y
patching file Apache-Test/lib/Apache/
Patch attempted to create file Apache-Test/lib/Apache/, which 
already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file 
patching file Apache-Test/lib/Apache/
patching file Apache-Test/lib/Apache/
patching file Apache-Test/lib/Apache/


David Wheeler                                     AIM: dwTheory                              ICQ: 15726394                         Yahoo!: dew7e
Kineticode. Setting knowledge in motion.[sm]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message