On 11/30/06, Hotz, Harry <[EMAIL PROTECTED]> wrote:
I have a new AIX 5.3 server that comes with a default Perl 5.82.
I have a DB2 programmer that has scripts from an old AIX 4.3 server that
used Perl 5.005_03. He will have to rewrite his scripts to use the new
Perl and asked me to install the old version side by side. I did so in a
usr/lpp/oldperl directory and compiled it successfully. He took the user
account under which the scripts are executing and added a path to the
profile to point to the location of the old Perl but when he uses it and
does a perl -version he still gets a return of the 5.8 version. He feels
this is a guarantee that his scripts will be hitting the wrong version
and wants to know why he cannot version query the old Perl.
My question is it even possible to successfully work with two
versions of Perl..5.005 and 5.8 on the same server...and I don't mean
just different modules. I saw that there is a use command to access
different module versions but I don't know if that applies to using the
whole Perl version. I do plan to insist he rewrite for the new version
soon but if I could do anything for him quickly to make his scripts use
the old version I will.
It's absolutely possible. In fact, it's recommended when upgrading.
The likely culprit here is the "bang path." He can alias the shell
variable, but if the first line of the script is still
#!/usr/bin/perl
then /usr/bin/perl is the Perl that will be used. What he needs to do
is go into the scripts that he's worried about and point them to
#!/usr/lpp/oldperl/perl5.005_03
...or wherever the actual executable for the old Perl is hiding. It
sounds like a lot of work, but he can automate it.
HTH,
-- jay
--------------------------------------------------
This email and attachment(s): [ ] blogable; [ x ] ask first; [ ]
private and confidential
daggerquill [at] gmail [dot] com
http://www.tuaw.com http://www.downloadsquad.com http://www.engatiki.org
values of β will give rise to dom!
