Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

Re: Upgrading Perl in production environment

by Abigail-II (Bishop)
on Mar 19, 2004 at 17:39 UTC ( [id://338080]=note: print w/replies, xml ) Need Help??


in reply to Upgrading Perl in production environment

Well, you could read perldelta, and keep tracks of the reported bugs on perlbug, but that doesn't mean you detect all things that break your programs.

But there are things you can do. First is to have a testing environment, and a solid test suite. This hopefully unearth things that break. But testing only determines breakage, it doesn't resolve them.

A better approach is to have each application (or set of applications) carry its own version of Perl. That is, you package an appropriate run-time environment of perl with your application. Then, if one application needs a newer version of Perl, no other application will break. Installing newer versions of modules won't break other applications. One can easily have different 'types' (64-bit ints, threads, dynamic library) of perl as well this way.

Abigail

  • Comment on Re: Upgrading Perl in production environment

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://338080]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (3)
As of 2025-06-14 14:56 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?
    erzuuliAnonymous Monks are no longer allowed to use Super Search, due to an excessive use of this resource by robots.