-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It's not really a problem only the error-message is missleading. Take
the following scenario:
* mp-1.29 installed
* mp-1.99_21 installed
Run perl Makefile.PL and you'll get a completely missleading error-message:
- ------------------------8<------------------------
perl Makefile.PL MP_APXS=/opt/apache2/bin/apxs
...
mod_perl/1.29 installation detected ... not ok
Cannot install mod_perl/1999.22 on top of mod_perl/1.29. .
...
- ------------------------8<------------------------
The problem is the time mod_perl is required ;-). The attached patch
solves this problem and the error-message makes sense.
Tom
Fred Moyer schrieb:
| Tom Schindl wrote:
|
|>Why doesn't it install if mp1 is installed? Now that we have a new
|>namespace that should not be a problem?
|
|
| What problem did you encounter? Can you post a sample of your attempted
| installation, or better yet a bug report as described here:
|
| http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
|
| - Phred
|
|
|>Tom
|>
|>Geoffrey Young schrieb:
|>| the mod_perl development team is pleased to announce the latest
|>version of
|>| mod_perl 2.0 - 2.0.0-RC5 - has been released.
|>|
|>| please note that this release contains substantial API changes,
making it
|>| incompatible with all prior mod_perl 1.99 releases to date. in other
|>words,
|>| you will need to modify ALL of your old 2.0 code before it will be
|>able to
|>| run with this latest release. fortunately, the changes required are
|>minor,
|>| straightforward, and simple.
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCX2sIkVPeOFLgZFIRArPCAJ9z3il0YGIQlTzTBldoJeieFk+GzQCfWZsg
ftURsP2eZ8nLtpBOkkgnEWM=
=GkJ3
-----END PGP SIGNATURE-----
16d15
< my $old_mp2 = eval { require Apache2 };
17a17
> my $old_mp2 = eval { require Apache2 };
