From owner-freebsd-ports@FreeBSD.ORG Sun Feb 26 20:31:05 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 70E8B16A420 for ; Sun, 26 Feb 2006 20:31:05 +0000 (GMT) (envelope-from chris@shenton.org) Received: from shenton.org (23.ebbed1.client.atlantech.net [209.190.235.35]) by mx1.FreeBSD.org (Postfix) with SMTP id A787F43D45 for ; Sun, 26 Feb 2006 20:31:04 +0000 (GMT) (envelope-from chris@shenton.org) Received: (qmail 1144 invoked by uid 1001); 26 Feb 2006 20:30:52 -0000 From: Chris Shenton To: freebsd-ports@freebsd.org Date: Sun, 26 Feb 2006 15:30:52 -0500 Message-ID: <86irr16ewz.fsf@Bacalao.shenton.org> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Finding packages affected by libtool13 -> libtool15 change? 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: Sun, 26 Feb 2006 20:31:05 -0000 Was updating a bunch of ports which suspiciously changed at once and I'm stuck in a prerequisite hell. I checked /usr/ports/UPDATING and see: 20060223: AFFECTS: all ports using libtool as part of the build process ... devel/libtool13 no longer exists. devel/libtool15 has been modified ... The main visible change will be that a large number of ports have had their plists modified (we now install libtool .la archives) and, as such, PORTREVISIONS have been bumped on ~2000 ports (roughly 1/7th of the tree). Unfortunately, there is no simple upgrade path. Short of removing all packages and reinstalling from scratch, the only other viable alternative would be careful use of portupgrade. Given the large number of different ways in which libtool is used by other ports in the tree, this is a process that is likely to vary considerably from system to system, and as such, folks should be very mindful of running automatic updating software, such as portupgrade, making extensive use of the -n flag (and equivalents for other updaters) to see what will actually be rebuilt, before actually performing the upgrade. Ouch. Is there a way to see which existing ports will need rebuilding, and what order they should be rebuilt to get the dependencies right? My trial-and-error approach to using portupgrade is very tedious and not very successful. I didn't see anything I thought I could use in pkg_info and pkgdb. Thanks.