Date: Mon, 27 Feb 2006 17:53:57 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Christopher Kelley <bsd@kelleycows.com> Cc: freebsd-ports@freebsd.org Subject: Re: libtool note in UPDATING Message-ID: <20060227225357.GA87738@xor.obsecurity.org> In-Reply-To: <440377FF.4020502@kelleycows.com> References: <440377FF.4020502@kelleycows.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=20 > me to basically say "There's no way to tell you how to successfully=20 > update your ports with the new libtool, hope you really understand how=20 > all the ports interact with each other, good night and good luck." >=20 > Now, I *DO* sort of understand the need for this change from reading the= =20 > entry, and I'm not arguing the fact that the change needed to be made. I= =20 > just don't know where to go from here because now I'm afraid to update=20 > any of my ports since I'm not sure I would understand the output of the= =20 > -n flag enough to figure out how to update my ports. >=20 > Is there a more straightforward explanation of how to upgrade ports with= =20 > 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 --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEA4MFWry0BWjoQKURAikZAJ9TssdNa1PDqOiH9OAj6/+2yITLTACcDgM9 YHNlNFoV8K1TlAtiiy3sDMI= =VT4n -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060227225357.GA87738>