From owner-freebsd-ports@FreeBSD.ORG Tue Feb 28 07:01:26 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 47C3216A420 for ; Tue, 28 Feb 2006 07:01:26 +0000 (GMT) (envelope-from bsd@kelleycows.com) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC2A43D4C for ; Tue, 28 Feb 2006 07:01:25 +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 (rwcrmhc12) with ESMTP id <20060228070124m120019msoe>; Tue, 28 Feb 2006 07:01:24 +0000 Message-ID: <4403F544.8090502@kelleycows.com> Date: Mon, 27 Feb 2006 23:01:24 -0800 From: Christopher Kelley User-Agent: Thunderbird 1.5 (X11/20060115) MIME-Version: 1.0 To: Kris Kennaway References: <440377FF.4020502@kelleycows.com> <20060227225357.GA87738@xor.obsecurity.org> In-Reply-To: <20060227225357.GA87738@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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 07:01:26 -0000 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. > > Kris > Kris, I'm sorry, but I'm only a hobbiest, (and working on a master's in mechanical engineering to boot) I just don't have the time to chance it. I'll wait for 6.1-RELEASE and do a complete reinstall. I'm familiar enough with that that I can do it fairly quickly. :) Christopher