From owner-freebsd-ports@freebsd.org Tue Aug 18 23:36:24 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4A4F9BDD07 for ; Tue, 18 Aug 2015 23:36:24 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B62C6125B for ; Tue, 18 Aug 2015 23:36:24 +0000 (UTC) (envelope-from marquis@roble.com) Received: from secure.postconf.com (mx5.roble.com [206.40.34.5]) by mx5.roble.com (Postfix) with ESMTP id 003386783C for ; Tue, 18 Aug 2015 16:36:17 -0700 (PDT) In-Reply-To: References: <55CF9848.3050302@groumpf.org> Date: Tue, 18 Aug 2015 16:36:18 -0700 Subject: Re: Perl 5.20 breaks /usr/bin/perl From: "Roger Marquis" To: freebsd-ports@freebsd.org Reply-To: marquis@roble.com MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Aug 2015 23:36:24 -0000 > Yes, it does not create a /usr/bin/perl symlink, starting with Perl 5.20. I'm curious about the logic behind this (automatic symlink removal without a large warning message)? It would seem to come with a high cost and little (any?) benefit. Shouldn't this at least be a dialog option? > If you still need one, and are not using some common shebang, like > /usr/local/bin/perl, which still works, or /usr/bin/env perl, which also > still works, create one yourself. /usr/bin/env may or may not work depending on the PATH it inherits. A symlink to /usr/bin would be best practice considering how many perl scripts specify this path, how many FreeBSD end-users are likely to be negatively impacted, how few might be positively impacted, and how it's removal will make it that much harder to advocate for FreeBSD's otherwise good cross-platform and cross-version compatibility. Roger