Date: Tue, 28 Feb 2006 12:27:17 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Kris Kennaway <kris@obsecurity.org> Cc: Christopher Kelley <bsd@kelleycows.com>, Jeremy Messenger <mezz7@cox.net>, freebsd-ports@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: libtool note in UPDATING Message-ID: <20060228122717.21f2cfd7@Magellan.Leidinger.net> In-Reply-To: <20060228014641.GA26933@xor.obsecurity.org> References: <440377FF.4020502@kelleycows.com> <20060227225357.GA87738@xor.obsecurity.org> <op.s5ntodyp9aq2h7@mezz.mezzweb.com> <20060228014641.GA26933@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Mon, 27 Feb 2006 20:46:41 -0500
schrieb Kris Kennaway <kris@obsecurity.org>:
> > >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.
> >
> > I doubt the 'portupgrade -a' will working on any ports that depend on
> > glib12, gtk12 and etc.
>
> Probably those all need portrevision bumps since the libraries changed
> name.
And interested parties can help to identify those ports by installing
sysutils/libchk and running it after the first "portupgrade -a" and
after (re)moving the libs in /usr/local/lib/compat/pkg. The resulting
output will list files or libs which point out missing libs. You can
then use "pkg_which <file>" to identify the port which needs to be
rebuild.
Bye,
Alexander.
--
Press every key to continue.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060228122717.21f2cfd7>