[Israel.pm] Perl version migration
kaminsky at math.huji.ac.il
Sun May 2 09:53:19 PDT 2004
Why not change just the first line of the old scripts, and rename the
old version of perl? You can even do it systematically: whenever you
install a new version of perl, change all the scripts which have
unqualified /usr/bin/perl to /usr/bin/perl<previous.version>
* Jason Elbaum <Jason.Elbaum at freescale.com> [02/05/04 15:10]:
> Omer Zak wrote:
> >Is it possible to have both Perl 5.8 and Perl 5.004 installed in your
> >system, and to have the old scripts invoke Perl 5.004?
> Thanks to everyone who commented on this.
> Sure, we can install new Perl alongside old Perl - that's what we have
> now for 5.6 (for example). The annoyance is that scripts which need a
> particular version have to point to it explicitly (
> #!/usr/local/bin/perl5.6.1 ) or they'll always get 5.004. On the other
> hand, if we just install new perl in place of old perl, we risk
> disturbing old scripts which may rely on features of 5.004 without even
> knowing it. And it's probably not realistic to review all our existing
> scripts and test them for transitioning to new versions of Perl.
> So is it *ever* possible to get out of this trap? Or will we be stuck
> forever with default perl at version 5.004, and new versions selected
> explicitly by the name of the perl executable?
> Jason Elbaum
> Freescale Semiconductor Israel (formerly Motorola Semiconductor)
> Perl mailing list
> Perl at perl.org.il
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams
Moshe Kaminsky <kaminsky at math.huji.ac.il>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://perl.org.il/pipermail/perl/attachments/20040502/eee12237/attachment.pgp
More information about the Perl