Tom Schindl wrote:
> 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:
right - the reason is sound (bad mp2 found) but
Tom Schindl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The reason to flip the lines is simply that you if you require mod_perl
before you modify the @INC using Apache2 the wrong mod_perl (the one of
mp1 is found). But that should be obvious, not?
Appologies, your logic seems sound. Thats
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The reason to flip the lines is simply that you if you require mod_perl
before you modify the @INC using Apache2 the wrong mod_perl (the one of
mp1 is found). But that should be obvious, not?
Tom
Tom Schindl schrieb:
| and here against current svn-trunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
and here against current svn-trunk.
Tom
Tom Schindl schrieb:
| The patch I submitted was against the Makefile.PL included into the
| distro rc5 and there it read the following:
|
| 8<
| my $old_mp2 = eval { requir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The patch I submitted was against the Makefile.PL included into the
distro rc5 and there it read the following:
- 8<
my $old_mp2 = eval { require Apache2 };
require mod_perl;
if( ) {
}
-
Philip M. Gollucci wrote:
I'll try to duplicate this soonish error locally soonish.
I just downloaded mp21.29 and apache1.3.33
cd mod_perl-1.29
perl Makefile.PL EVERYTHING=1
answer y both questions
make install
next the mp2 and httpd2 part
cd mod_perl2
perl Makefile.PL \
MP_APXS=/home/pgoll
Tom Schindl wrote:
Index: Makefile.PL
===
--- Makefile.PL (revision 161423)
+++ Makefile.PL (working copy)
@@ -14,8 +14,8 @@
BEGIN {
eval {
require mod_perl;
+if ($mod_perl::VERSION < 1.999_22 && $old_mp2) {
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?
>incompatible with all prior mod_perl 1.99 releases to date. in
I'm hoping you read that wrong as 1.99 is actually mp2.
Please forgive me if I didn't give you enough cr
-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<
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/us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why doesn't it install if mp1 is installed? Now that we have a new
namespace that should not be a problem?
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 rel
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 AL
12 matches
Mail list logo
