From owner-freebsd-ports@FreeBSD.ORG Sun Jan 30 16:13:22 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 2AE0C16A4CE; Sun, 30 Jan 2005 16:13:22 +0000 (GMT) Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A48343D2D; Sun, 30 Jan 2005 16:13:21 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-b.dmv.com (mail-gw-cl-b.dmv.com [216.240.97.39]) j0UGPQWa072932; Sun, 30 Jan 2005 11:25:26 -0500 (EST) (envelope-from sven@dmv.com) Received: from [64.45.134.154] (dogpound.dyndns.org [64.45.134.154]) by mail-gw-cl-b.dmv.com (8.12.9/8.12.9) with ESMTP id j0UGDKeE060017; Sun, 30 Jan 2005 11:13:20 -0500 (EST) (envelope-from sven@dmv.com) Message-ID: <41FD07A0.2060809@dmv.com> Date: Sun, 30 Jan 2005 11:13:20 -0500 From: Sven Willenberger User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: perl@freebsd.org References: <20050129202425.GA56998@heechee.tobez.org> In-Reply-To: <20050129202425.GA56998@heechee.tobez.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 216.240.97.42 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.39 cc: freebsd-stable@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: Sun, 30 Jan 2005 16:13:22 -0000 Anton Berezin wrote: > > In order to keep pkg-install simple, no old symlink chasing and removal > will be done, although the detailed instructions will be posted in > ports/UPDATING and in pkg-message for the ports. > How about leaving it up to the installer? Much like the minicom port prompts the user if they would like to symlink a /dev/modem device, why not ask (post-install) "Would you like to make a symlink in /usr/bin to your new installation?" or as someone else has suggested add a make flag (make ADD_SYMLINK=yes). Those who wish to have an unpolluted /usr/bin can not opt for a symlink, those that want compatibility with a majority of the scripts already written can have the link created. Just a thought, Sven