From owner-freebsd-perl@FreeBSD.ORG Sun Jan 30 10:53:30 2005 Return-Path: Delivered-To: freebsd-perl@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7E7D16A4CE; Sun, 30 Jan 2005 10:53:30 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C43443D1F; Sun, 30 Jan 2005 10:53:30 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1CvChn-000Njg-7Z; Sun, 30 Jan 2005 11:53:23 +0100 Date: Sun, 30 Jan 2005 11:53:23 +0100 From: Kirill Ponomarew To: Holger Kipp Message-ID: <20050130105323.GB62253@voodoo.oberon.net> References: <20050129202425.GA56998@heechee.tobez.org> <41FC75E9.3060601@freebsd.org> <20050130104732.GA30800@intserv.int1.b.intern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050130104732.GA30800@intserv.int1.b.intern> X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE cc: freebsd-stable@freebsd.org cc: perl@freebsd.org cc: Scott Long cc: freebsd-ports@freebsd.org Subject: Re: [HEADS UP] perl symlinks in /usr/bin will be gone X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2005 10:53:31 -0000 On Sun, Jan 30, 2005 at 11:47:32AM +0100, Holger Kipp wrote: > > I'm fine with this plan for 6-CURRENT. For 5-STABLE, it's a major > > user-visible change, and that is something that we promised to avoid > > with stable branches. > > It violates POLA on 5-STABLE, and it will violate POLA on 6-CURRENT, > especially as most perl programmers assume /usr/bin/perl to be the > correct path. If it's linux tradition to put perl in this path, perl programmers should assume another path on FreeBSD, so it isn't an argument for the proposed change. > We had enough good arguments against this change already, so imho > the correct thing to do is do just what Kris asked for: remove the > _dangling_ symlinks. -Kirill