From owner-freebsd-ports@FreeBSD.ORG Sat Jan 29 22:17:16 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AA016A4CF; Sat, 29 Jan 2005 22:17:16 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BFA43D4C; Sat, 29 Jan 2005 22:17:15 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id 6C7F946B2A; Sat, 29 Jan 2005 17:17:15 -0500 (EST) Date: Sat, 29 Jan 2005 22:16:39 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Oliver Lehmann In-Reply-To: <20050129220905.46ab86ae.lehmann@ans-netz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: perl@FreeBSD.org cc: freebsd-stable@FreeBSD.org cc: tobez@FreeBSD.org cc: freebsd-ports@FreeBSD.org Subject: Re: [HEADS UP] perl symlinks in /usr/bin will be gone X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jan 2005 22:17:16 -0000 On Sat, 29 Jan 2005, Oliver Lehmann wrote: > Anton Berezin wrote: > > > In practical terms this will mean a one-time sweep of your scripts in > > order to convert them, in a typical case, from #! /usr/bin/perl to > > #! /usr/local/bin/perl. > > Wouldn't that break most of the 3rd party scripts out in the world? The following URL: http://www.googlefight.com/cgi-bin/compare.pl?q1=%23%21%2Fusr%2Fbin%2Fperl&q2=%23%21%2Fusr%2Fbin%2Fenv+perl&B1=Make+a+fight%21&compare=1&langue=us Suggests firmly that the answer to that question is yes. What worries me particularly about the proposed change is that it requires administrators to touch the scripts of their user's files as part of an upgrade -- this is not a good situation for an ISP to be put in. That or to immediately re-add the symlink on the basis that the practical reality is that (despite some limited documentation to the contrary), that's the way everyone runs perl. I have the suspicion that while removing this symlink may encourage programming cleanliness, it's going to shoot a lot of feet unnecessarily. Also, since env isn't a built-in, it means exec runs twice for every perl script, not once... Robert N M Watson