From owner-freebsd-current Thu Mar 21 10:56:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA18763 for current-outgoing; Thu, 21 Mar 1996 10:56:29 -0800 (PST) Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA18758 for ; Thu, 21 Mar 1996 10:56:26 -0800 (PST) Received: (from Unemeton@localhost) by perki.connect.com.au id FAA10441 (8.6.12/IDA-1.6); Fri, 22 Mar 1996 05:55:31 +1100 >Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id TAA05488; Thu, 21 Mar 1996 19:32:02 +1100 Message-Id: <199603210832.TAA05488@nemeton.com.au> To: bmk@transport.com Subject: Re: perl4 In-reply-to: <199603202241.OAA02668@dtr.com> Date: Thu, 21 Mar 1996 19:32:01 +1100 From: Giles Lean Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 20 Mar 1996 14:41:45 -0800 (PST) "Brant M. Katkansky" wrote: > * Leave things the way they are, and keep perl4 as the standard perl. > Perl5 can be installed in /usr/local as a package. > Do this, but rename /usr/bin/perl to /usr/bin/perl4 (and symlink it to /usr/bin/perl5.036 -- what happened to that?). Then the FreeBSD scripts in /usr/bin etc can invoke #! /usr/bin/perl4 and a user installing perl5 into /usr/local/bin won't be surprised. This solution "works" for our existing scripts, doesn't bloat the distribution and looks less out of date since we're clearly shipping perl4 on purpose. User scripts with #! /usr/bin/perl won't work until something is done; we might need a "use perl4 or install perl5" sort of script as /usr/bin/perl for one release. Giles