Date: Wed, 29 Mar 2006 11:58:29 +0200 From: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@freebsd.org, Amarendra Godbole <amarendra.godbole@gmail.com> Subject: Re: Broken dependency on expat. Message-ID: <442A5A45.1050808@gmx.de> In-Reply-To: <20060329045038.GA45765@xor.obsecurity.org> References: <294439d20603282038i6026c5bai3ddf4263def23548@mail.gmail.com> <20060329045038.GA45765@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Wed, Mar 29, 2006 at 04:38:29AM +0000, Amarendra Godbole wrote: >> Hi, >> >> I tried to build apache22 from the ports (/usr/ports/www/apache22/). >> Now, the initial build failed, because of a broken dependency on >> libexpat - as apache22 needed a newer version than the one I had >> (1.95.*). >> >> So, I forcibly deinstalled, and reinstalled expat2 from >> /usr/ports/textproc/expat2/, and apache22 built and installed fine. >> >> So far so good... >> >> ...but upgrading libexpat removed the original libexpat.so.5 link, and >> put a libexpat.so.6...which caused all my X based programs, including >> the window manager to break! X just refused to start, and so did many >> other programs. >> >> Now, I just put back the softlink libexpat.so.5, and poof...things >> were up and running again... >> >> So my question is: is there a better way to handle such a scenario? Or >> in case of libraries, can't the original links be preserved, and new >> links added (I guess this cannot be done). > > Use portupgrade. > > Kris Portupgrade will keep the old libs around. Since I have a small HD I prefer to get rid of old libs and add an entry to "/etc/libmap.conf". Using links to handle this doesn't look like a good solution to me, because they might be forgotten and left on the system long beyond their usefulness.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442A5A45.1050808>