I have a client whose Production and Development Server version of Perl
is significantly out of data particularly with libraries (even though
they are running Perl 5.8.0). This become obvious when I moved my
program on my Mac at 5.8.8 with its current libraries to their
development server. Even though it all worked, a lot of error messages
started appearing in the Apache logs. As a good programmer, I started to
fix them only to find they were experiencing these errors all the time
with all their other programs. Investigating it more, I discovered that
their libraries were severely out of date. For example their version of
manip.pm is dated 2000.
I have propose that they install on their Development Linux server a
later version of Perl in another location and migrate the application
over (e.g. /usr/new/perl). Their concern is there is only one MySQL
program, but the Perl libraries to access it would be different.
Second, they think installing a later version of Perl in a different
location would overwrite the current library. I am not really clear how
Perl locates its install Libraries, so I would like some clarification
on this issue with two different versions running. Is there a setup
method with Perl to make sure this does not happen? They will probably
use CPAN to add the new libraries. How should this be set up? Another
issue is they are using a MySQL 4.x version. Not a MySQL 5.x version. On
my Mac, I had to load DBI and DBD driver for MySQL 5 and update MySQL to
5.x. But I suppose I can get older versions from CPAN.

Signature
------------------------------------------------------------------------
*Michael Barto*
Software Architect
LogiQwest Circle
LogiQwest Inc.
16458 Bolsa Chica Street, # 15
Huntington Beach, CA 92649
http://www.logiqwest.com/
mbarto@logiqwest.com <mailto:mbarto@logiqwest.com>
Tel: 714 377 3705
Fax: 714 840 3937
Cell: 714 883 1949
*'tis a gift to be simple*
------------------------------------------------------------------------
This e-mail may contain LogiQwest proprietary information and should be
treated as confidential.
Brian D Foy - 14 Jan 2008 21:12 GMT
> over (e.g. /usr/new/perl). Their concern is there is only one MySQL
> program, but the Perl libraries to access it would be different.
There are already multiples ways to access a database server.
> Second, they think installing a later version of Perl in a different
> location would overwrite the current library. I am not really clear how
> Perl locates its install Libraries,
It asks you at configure time where you want to put them.
I put all my perls in /usr/local/perls, each with their completely
separate trees of modules, executables, and so on. I leave alone
Apple's perl and link /usr/local/bin/perl to the one I want to use most
of the time. I make other links to particular versions, such as
/usr/local/bin/perl5.10.0.
I have to install modules multiple times, but that is no big deal. I
start cpan(1) with the right perl and it finds the right CPAN/Config.pm
and installs them in the right place:
$ perl5.10.0 cpan ...