in reply to Multiple Perl Installations

Assuming you haven't moved things around since installing perl5.6.1, the reason that Apache cannot find the libraries in the 5.6.1 directories is that the web server is running the perl5.6.0. If you actually manage to get perl5.6.0 to look in the 5.6.1 directories, you will then be running perl5.6.0 with the perl5.6.1 libraries, which seems like a bad idea. (If you built 5.6.1 and then moved the directories around, your perl installation will be all confused because the contents of @INC are compiled into the perl binary.)

I've thought of a few possible solutions:

You haven't given details about the problems you experienced when you upgraded to 5.6.1 previously, but I would like to point out that perl5.6.1 fixes many bugs from the 5.6.0 release; see the 5.6.1 perldelta for more details.

* I don't know a lot about Apache; I suppose it may be possible to get Apache running with perl5.6.1 instead of perl5.6.0 without rebuilding the web server.

Replies are listed 'Best First'.
(tye)Re: Multiple Perl Installations
by tye (Sage) on Jul 02, 2001 at 00:07 UTC
    "I fear that the reports of my demise have been greatly exagerated."

    - The CPAN.pm bug

    So, has it really been fixed this time? It was reported fixed and appeared to have been fixed but when 5.6.1 came out it appeared that the part of the bug fix that was required on the CPAN mirror sites had not been kept up and so the bug appeared again. Indeed, the first "fix" is certainly contained in 5.6.0's CPAN.pm.

    So, do we now have a second fix?

    And for those of you thinking, "Why don't you just check for yourself, ya lazy Saint??", the ChangeLog for the latest version of CPAN.pm according to http://search.cpan.org/ doesn't show any changes since March 1999, which was before the first fix.

            - tye (but my friends call me "Tye")