From owner-freebsd-perl@FreeBSD.ORG Sat Jan 29 21:28:09 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 C577816A4CE; Sat, 29 Jan 2005 21:28:09 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 853E743D39; Sat, 29 Jan 2005 21:28:09 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1Cv08Y-000EEr-Sk; Sat, 29 Jan 2005 22:28:10 +0100 Date: Sat, 29 Jan 2005 22:28:10 +0100 From: Kirill Ponomarew To: Kris Kennaway Message-ID: <20050129212810.GA54501@voodoo.oberon.net> References: <20050129202425.GA56998@heechee.tobez.org> <20050129205807.GA36637@xor.obsecurity.org> <20050129205940.GB56998@heechee.tobez.org> <20050129210352.GA36709@xor.obsecurity.org> <20050129210848.GC56998@heechee.tobez.org> <20050129211634.GB38050@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050129211634.GB38050@xor.obsecurity.org> X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE cc: perl@FreeBSD.org cc: freebsd-ports@freebsd.org cc: Anton Berezin 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: Sat, 29 Jan 2005 21:28:09 -0000 On Sat, Jan 29, 2005 at 01:16:34PM -0800, Kris Kennaway wrote: > > The thing is, that the whole idea of touching /usr/bin at all made sense > > when perl was in the base system and we needed a way to "replace" it > > with a version from ports. > > > > Since we don't have it in the base for quite some time, there is no good > > reason to continue cluttering /usr/bin with those symlinks. So this > > needs to be done eventually, and this seemed as good time as any to > > introduce this change. > > Maybe we should continue to create (and also remove) the links for 5.x > and try the change out in 6.x to see what kind of an impact is has. In this case we can miss what ports are actually broken, since not everyone is running 6.x. -Kirill