From owner-freebsd-ports@FreeBSD.ORG Tue Feb 28 01:40:47 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 E5ECF16A420 for ; Tue, 28 Feb 2006 01:40:47 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from centrmmtao06.cox.net (centrmmtao06.cox.net [70.168.83.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B1F143D4C for ; Tue, 28 Feb 2006 01:40:47 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by centrmmtao06.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060228014042.TJIA4002.centrmmtao06.cox.net@mezz.mezzweb.com>; Mon, 27 Feb 2006 20:40:42 -0500 Date: Mon, 27 Feb 2006 19:42:03 -0600 To: "Kris Kennaway" References: <440377FF.4020502@kelleycows.com> <20060227225357.GA87738@xor.obsecurity.org> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20060227225357.GA87738@xor.obsecurity.org> User-Agent: Opera M2/8.52 (Linux, build 1631) Cc: Christopher Kelley , freebsd-ports@freebsd.org 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 01:40:48 -0000 On Mon, 27 Feb 2006 16:53:57 -0600, Kris Kennaway wrote: > On Mon, Feb 27, 2006 at 02:06:55PM -0800, Christopher Kelley wrote: >> Am I reading the entry for libtool in UPDATING correctly? It seems to >> me to basically say "There's no way to tell you how to successfully >> update your ports with the new libtool, hope you really understand how >> all the ports interact with each other, good night and good luck." >> >> Now, I *DO* sort of understand the need for this change from reading the >> entry, and I'm not arguing the fact that the change needed to be made. I >> just don't know where to go from here because now I'm afraid to update >> any of my ports since I'm not sure I would understand the output of the >> -n flag enough to figure out how to update my ports. >> >> Is there a more straightforward explanation of how to upgrade ports with >> the new libtool? > > Basically, portupgrade -a should be OK (but watch out for the perl > upgrade as well, i.e. read that entry too). If you run into problems > let us know; I'd like to refine that entry with a working prescription > before the release. I doubt the 'portupgrade -a' will working on any ports that depend on glib12, gtk12 and etc. I would go with -af or -afr to force rebuild all apps if you want to use portupgrade instead remove ports and reinstall stuff as suggested in the UPDATING. Cheers, Mezz > Kris -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org