From owner-freebsd-questions@FreeBSD.ORG Fri Mar 5 15:22:13 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 389F7106566C for ; Fri, 5 Mar 2010 15:22:13 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail4.sea5.speakeasy.net (mail4.sea5.speakeasy.net [69.17.117.6]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1F48FC22 for ; Fri, 5 Mar 2010 15:22:12 +0000 (UTC) Received: (qmail 2830 invoked from network); 5 Mar 2010 15:22:12 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail4.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Mar 2010 15:22:12 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id F08C9508A7 for ; Fri, 5 Mar 2010 10:22:05 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 6411A1CCBA; Fri, 5 Mar 2010 10:22:05 -0500 (EST) From: Lowell Gilbert To: FreeBSD Mailing List References: <4B8FDA6A.9090308@tundraware.com> <4B8FDC32.6090204@eskk.nu> <4B8FE844.6060804@tundraware.com> <4B8FEA40.9040203@infracaninophile.co.uk> Date: Fri, 05 Mar 2010 10:22:05 -0500 In-Reply-To: <4B8FEA40.9040203@infracaninophile.co.uk> (Matthew Seaman's message of "Thu, 04 Mar 2010 17:13:36 +0000") Message-ID: <44d3zix082.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Perl 5.8 -> 5.10 On Current Production System X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2010 15:22:13 -0000 Matthew Seaman writes: > You got bitten by an ill-considered change introduced after the UPDATING > instructions were written. To work around it, you need to set > DISABLE_CONFLICTS when rebuilding the port, eg like this: > > # portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f perl-5.8\.* > > Please feel free to complain volubly about this: it's hand-holding for > newbies which annoys and incoveniences the vastly larger number of > non-newbies (ie. anyone who has been using the ports for more than a few > weeks.) It has occurred to me that teaching portupgrade to handle this would be a Simple Matter of Programming. Maybe even a strategy as simple as adding the variable to the make command lines automatically any time '-o' is specified. I wonder whether I could write that change without actually learning ruby... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/