From owner-freebsd-ports@FreeBSD.ORG Tue Feb 28 06:58:00 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org 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 9F58616A420; Tue, 28 Feb 2006 06:58:00 +0000 (GMT) (envelope-from bsd@kelleycows.com) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.77.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4811C43D67; Tue, 28 Feb 2006 06:57:57 +0000 (GMT) (envelope-from bsd@kelleycows.com) Received: from [10.3.29.200] (c-24-30-114-96.hsd1.ca.comcast.net[24.30.114.96]) by comcast.net (sccrmhc13) with ESMTP id <20060228065756013001kt29e>; Tue, 28 Feb 2006 06:57:56 +0000 Message-ID: <4403F473.8010404@kelleycows.com> Date: Mon, 27 Feb 2006 22:57:55 -0800 From: Christopher Kelley User-Agent: Thunderbird 1.5 (X11/20060115) MIME-Version: 1.0 To: freebsd-ports@FreeBSD.org References: <440377FF.4020502@kelleycows.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Ade Lovett Subject: Re: libtool note in UPDATING X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 06:58:00 -0000 Ade Lovett wrote: > > On Feb 27, 2006, at 14:06 , Christopher Kelley wrote: >> Is there a more straightforward explanation of how to upgrade ports >> with the new libtool? > > That *is* the straightforward way of explaining it :) > > libtool is one of a handful of ports that is used so extensively by > the rest of the tree that providing a one-click method that's going to > work in every situation is an exercise in futility. Around 1400 ports > were directly affected by the change, with several hundred more having > varying degrees of collateral damage (which, as far as I know, has all > been fixed as of the time of writing). That's greater than 10% of the > tree as a whole. > > Judicious use of portupgrade and its ilk may certainly work in your > case, but there are absolutely no guarantees that something, > somewhere, in the rebuild will go wrong, and result in a rather messed > up set of packages on the system. > > If you want to be absolutely, positively sure, I'm afraid there is > only one simple solution, involving the archival of any configuration > files that may have been changed locally, followed by saving off a > list of the ports/packages installed on the system, then "rm -rf > /var/db/pkg/* /usr/local /usr/X11R6 /usr/compat/*" and building > everything from scratch. I tested both this method, and the > portupgrade method, on two identically configured scratch boxes with a > few hundred ports installed on both, and the sledgehammer approach was > in fact considerably faster. > >> Also, will 6.1-RELEASE have this change already in the ports tree >> that it ships with? > > Yes. This also offers a third solution. Wait until 6.1-RELEASE comes > out, along with its associated package sets, and do a clean install > from there. Ditto for 5.5-RELEASE if there is some reason to keep a > machine on the 5.x branch as opposed to jumping to 6.x > > -aDe > > Which is, in fact, the solution I think I'm going to take. I had planned on upgrading my last machine from 5.4 to 6.1 anyway, so that one wasn't a concern, but I had hoped to avoid the reinstall for my other (unfortunately very much slower) machines. Thanks to everyone for all the suggestions and input. I'm sorry that I don't have time to try some of the suggestions that have been made, this seems to be the fastest and simplest method. Christopher