|P is for Practical|
Smooth perl upgradesby saintmike (Vicar)
|on Dec 15, 2004 at 18:32 UTC||Need Help??|
saintmike has asked for the wisdom of the Perl Monks concerning the following question:
Fellow monks, has anyone worked through seamless perl upgrades on large systems?
If there's a large number of different Perl applications on a box, all using #!/usr/bin/perl (which is 5.00503) and I want to upgrade to 5.8.6, obviously I can't just replace #!/usr/bin/perl by perl 5.8.6, because that might break certain scripts only happy with perl 5.00503.
So, during a transition period, I need to support both /usr/bin/perl (5.00503) and, say, /some/other/path/bin/perl which is 5.8.6.
Old scripts are unchanged with #/!usr/bin/perl, new scripts will be using #!/some/other/path/bin/perl.
So far so good. Now let's look at the modules. Both installations are going to use different lib paths, so in order to install a new module on the box (like a security fix of a CPAN module), it needs to be installed for both perl5.00503 and perl5.8.6 (lets hope it works for both of them).
Now let's say that perl 5.10.0 becomes available. I'll add yet another perl install with its own lib directory, and now have to potentially upgrade three installs with every new module.
The problem is obviously that there's applications which no one wants to touch and therefore old perl installs have to be maintained (almost) indefinitely, slowly transitioning into a maintenance nightmare.
Has anyone in the monastry worked through transition periods like these and successfully managed them without going crazy?