From owner-freebsd-ports@FreeBSD.ORG Tue Feb 28 01:46:43 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 C0CE416A420 for ; Tue, 28 Feb 2006 01:46:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA2D43D58 for ; Tue, 28 Feb 2006 01:46:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9D3A91A4E41; Mon, 27 Feb 2006 17:46:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C1A1353666; Mon, 27 Feb 2006 20:46:41 -0500 (EST) Date: Mon, 27 Feb 2006 20:46:41 -0500 From: Kris Kennaway To: Jeremy Messenger Message-ID: <20060228014641.GA26933@xor.obsecurity.org> References: <440377FF.4020502@kelleycows.com> <20060227225357.GA87738@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Christopher Kelley , freebsd-ports@freebsd.org, Kris Kennaway 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:46:43 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 27, 2006 at 07:42:03PM -0600, Jeremy Messenger wrote: > On Mon, 27 Feb 2006 16:53:57 -0600, Kris Kennaway = =20 > wrote: >=20 > >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. >=20 > I doubt the 'portupgrade -a' will working on any ports that depend on =20 > glib12, gtk12 and etc. Probably those all need portrevision bumps since the libraries changed name. Kris --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEA6uBWry0BWjoQKURAjRlAJwNN4XiFImK2npTj0L5P296vmVDOQCg6f1e sSZs32n+wc6TJY9SOs7Njc4= =mli0 -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp--