Date: Mon, 27 Feb 2006 20:46:41 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Jeremy Messenger <mezz7@cox.net> Cc: Christopher Kelley <bsd@kelleycows.com>, freebsd-ports@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: libtool note in UPDATING Message-ID: <20060228014641.GA26933@xor.obsecurity.org> In-Reply-To: <op.s5ntodyp9aq2h7@mezz.mezzweb.com> References: <440377FF.4020502@kelleycows.com> <20060227225357.GA87738@xor.obsecurity.org> <op.s5ntodyp9aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <kris@obsecurity.org> = =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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060228014641.GA26933>