----- Original Message ----- From: "Randal L. Schwartz" <merlyn@stonehenge.com>
To: "Issac Goldstand" <[EMAIL PROTECTED]>
Cc: <advocacy@perl.apache.org>; "Andreas J Koenig" <[EMAIL PROTECTED]>; "mod_perl Mailing List" <modperl@perl.apache.org>; "Stas Bekman" <[EMAIL PROTECTED]>
Sent: Tuesday, December 28, 2004 7:09 PM
Subject: Re: About putting the blame on other shoulders
"Issac" == Issac Goldstand <[EMAIL PROTECTED]> writes:
Issac> Which is exactly the point that I was trying to make: This *should* be
Issac> doable. The fact that it's *not* means that Perl is a monolithic
Issac> library and can't have 2 sets of "extensions" in the same site
Issac> installation.
*Or* in the CPAN, or visible to perldoc, or with installed manpages. See, the whole toolchain presumes "Apache::Request" or "mod_perl" means precisely one thing.
Just like when GD2 was put out 2 1/2 years ago, there was only the old "GD" in CPAN, and I had the same problems - I had to check every piece of code I wrote for GD, and rewrite it to work with the new GD, as well as specify that I now "use GD 2;" thus destroying any backwards compatability.
It doesn't matter how many Perl installations you have on your disk. There's only one CPAN. Perrin's point, while valid, doesn't address the indexing issue.
But the indexer *does* handle it. If I want to install an old version of GD, because I can't install libgd2, I can still do "install L/LD/LDS/GD-1.41.tar.gz" (finding the path is usually easy, unless maintainers were switched: just do "m GD") It would be still better, IMHO, if I could just do "install GD-1.41". The problem is that modules/programs which want GD-1.xx will choke on GD-2.xx and vice versa (and I can only have one in the site installation at the same time). And to make things worse, the "use module version" pragma only goes one way: up.
Issac
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
