----- Original Message ----- From: "Randal L. Schwartz" <merlyn@stonehenge.com>
To: "Stas Bekman" <[EMAIL PROTECTED]>
Cc: <advocacy@perl.apache.org>; "Andreas J Koenig" <[EMAIL PROTECTED]>; "mod_perl Mailing List" <modperl@perl.apache.org>
Sent: Tuesday, December 28, 2004 6:43 PM
Subject: Re: About putting the blame on other shoulders
"Stas" == Stas Bekman <[EMAIL PROTECTED]> writes:
Stas> Unfortunately thanks to Randal, people are now totally confused.
No, I think thanks to me, people are now aware of a problem of fundamental incompatibility between the "single @INC" historical legacy of the entire Perl world and toolchain, and your "use Apache2" workaround. There's awareness, not confusion. I think *you* are trying to confuse the issue by saying there's not a single thing wrong with your proposed release of MP2. Yes, there wouldn't be, if the entire rest of the world was compatible with it, which it isn't.
Here are some possible scenarios:
1) you don't budge, CPAN doesn't change, and people around the world get confused with your release, because it's asking them to "upgrade" their mp1 by installing mp2, which *cannot* be done.
Which is exactly the point that I was trying to make: This *should* be doable. The fact that it's *not* means that Perl is a monolithic library and can't have 2 sets of "extensions" in the same site installation. Which means that libperl.so is something which shouldn't exist, since it implies some "sharedness" - but what it's really providing is a shared library interface with static extensions. By linking against libperl.so (or whatever), you're essentially dooming your applications to being stuck with whatever CPAN throws its way.
Issac
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
