|Do you know where your variables are?|
Finally! Saying goodbye to perl 5.005by the_slycer (Chaplain)
|on May 05, 2005 at 15:09 UTC||Need Help??|
the_slycer has asked for the wisdom of the Perl Monks concerning the following question:
I (and others) have finally convinced the PHB's that moving our legacy perl 5.005 system, running in production on machines that nobody knows how to rebuild (short of mirroring the drive), on Redhat 6.2, using an ancient version of apache & mod_perl, would be a good thing.
It might be nice to have development machines that are running the same version as test, which could be running the same version as production.. go figure.
Because I was vocal about this (we have been bit a few times by stuff passing test, but failing on production due to module versions - don't even get me started on use warnings failing...), I get to run with the project.
I am aware of some of the problems, for example, not having the LANG environment variable set to sane things causes wierd errors in perl 5.8.0 that were never there in 5.005, but I also have never had the opportunity to handle a migration before.
What kinds of things am I going to have to watch out for? Has anybody been through an upgrade like this? We use mod perl with apache 1, the new machines have apache 2 by default, should we revert to apache 1? What kinds of things might we get bit by with apache2/mod_perl2 vs apach1/mod_perl1.
Just an FYI, we have upwards of 200k lines of source code, and no regression testing built around the system, so I can't just put it on and see what works, I'd like to get an idea of problem spots that I'll need to look at.
Any suggestions would be welcome!
update: Ok, advice taken, no mod_perl_2 will be the plan. Any other gotchas moving from 5.005 to 5.8.0?