Hi,
I have got a new server that I want to put into production. To comply
with the manufacturer, I have installed RedHat 6.1 on it. Up till now
we have used Debian based machines and have been using the system
perl. That worked ok because all the necessay libperl*.deb could be
installed via the
Perl 5.10 isn't really supported any more, so it is highly likely that at some
stage the system Perl will get upgraded behind the scenes, breaking binary
compatibility with modules even if they are in local::lib. The only safe
solution is to use your own Perl (I'd not put it directly under
On 09/30/2011 10:52 AM, Stuart Watt wrote:
Perl 5.10 isn't really supported any more, so it is highly likely
that at some stage the system Perl will get upgraded behind the
scenes, breaking binary compatibility with modules even if they are
in local::lib. The only safe solution is to use your
Hi Dermot,
in my development machine I have a Perl environment installed in my home
dir with perlbrew. That way I can install anything I need without
disturbing (or using) the system perl. Later, when doing a deployment to
the production environment, I deploy my app and my full perlbrew
On Fri, Sep 30, 2011 at 10:00 AM, Joe Landman
land...@scalableinformatics.com wrote:
For years, we've been putting our Perl under the
/opt/scalable/
tree. We've run into so many problems with system supplied Perl, that in
general, we simply ignore it. We also have, in the past
=-fPIC -Doptimize=-O2 \
-Duseshrplib -Dcf_by=Your_name_here \
-Dcf_email=Your_email@here
-Original Message-
From: Dermot [mailto:paik...@googlemail.com]
Sent: Friday, September 30, 2011 10:39 AM
To: The elegant MVC web framework
Subject: [Catalyst] How best not to use the system perl
Hi
