From owner-freebsd-current Thu May 9 10:18: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id E8B7937B404; Thu, 9 May 2002 10:17:56 -0700 (PDT) Date: Thu, 9 May 2002 10:17:56 -0700 From: David O'Brien To: current@FreeBSD.ORG Subject: Re: The future of perl on FreeBSD Message-ID: <20020509101756.A61913@hub.freebsd.org> References: <20020509180605.A57805@energyhq.homeip.net> <20020509191631.A58805@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020509191631.A58805@energyhq.homeip.net>; from flynn@energyhq.homeip.net on Thu, May 09, 2002 at 07:16:31PM +0200 X-Operating-System: FreeBSD 4.5-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, May 09, 2002 at 07:16:31PM +0200, Miguel Mendez wrote: > > Ports should avoid messing with stuff outside of ${PREFIX} if they can > > help it. Existing systems will already have a /usr/bin/perl on them > > unless the user goes and removes it. People writing or executing scripts for > > new systems can easily figure out something is wrong when they get: > > Now that I think of it, you are absolutely right, John. Just let's make > a big big banner saying "Perl is no longer in base" so everybody notices Ok, then. What is so wrong with /usr/bin/perl being "/usr/bin/env perl", or DES's wrapper? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message