Date: Sun, 26 Feb 2006 15:43:15 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Chris Shenton <chris@shenton.org> Cc: freebsd-ports@freebsd.org Subject: Re: Finding packages affected by libtool13 -> libtool15 change? Message-ID: <20060226204315.GA15089@xor.obsecurity.org> In-Reply-To: <86irr16ewz.fsf@Bacalao.shenton.org> References: <86irr16ewz.fsf@Bacalao.shenton.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 26, 2006 at 03:30:52PM -0500, Chris Shenton wrote: > Was updating a bunch of ports which suspiciously changed at once and > I'm stuck in a prerequisite hell. I checked /usr/ports/UPDATING and > see:=20 >=20 > 20060223: > AFFECTS: all ports using libtool as part of the build process > ... > devel/libtool13 no longer exists. devel/libtool15 has been modified > ... > The main visible change will be that a large number of ports have > had their plists modified (we now install libtool .la archives) > and, as such, PORTREVISIONS have been bumped on ~2000 ports (roughly > 1/7th of the tree). >=20 > Unfortunately, there is no simple upgrade path. Short of removing > all packages and reinstalling from scratch, the only other viable > alternative would be careful use of portupgrade. Given the large > number of different ways in which libtool is used by other ports > in the tree, this is a process that is likely to vary considerably > from system to system, and as such, folks should be very mindful > of running automatic updating software, such as portupgrade, making > extensive use of the -n flag (and equivalents for other updaters) > to see what will actually be rebuilt, before actually performing > the upgrade. >=20 > Ouch. Is there a way to see which existing ports will need rebuilding, > and what order they should be rebuilt to get the dependencies right? >=20 > My trial-and-error approach to using portupgrade is very tedious and > not very successful. I didn't see anything I thought I could use in > pkg_info and pkgdb.=20 Start with portupgrade -a (or portupgrade -na) as the above recommends, if you don't want to just blindly plunge in. Kris --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEAhLjWry0BWjoQKURAqJMAKCmWyN4MahZi6j6qwI2BnlZ9KB+MQCggs41 pPk1h+4PK0+zvlUTGsBBY0Q= =kz/7 -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060226204315.GA15089>