Date: Fri, 30 Mar 2007 02:01:52 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: the art of pkgdb -F Message-ID: <20070330020152.4f268b66@gumby.homeunix.com> In-Reply-To: <20070329164106.27389f8a@localhost> References: <20070328011712.GR11147@tigger.digitaltorque.ca> <20070327202842.1678265c.freebsd@dfwlp.com> <d7195cff0703272219r3e504bd5tb09ca5acd3f82776@mail.gmail.com> <20070328212432.669353e4@gumby.homeunix.com> <20070329003659.GW11147@tigger.digitaltorque.ca> <20070329121553.070a6321@localhost> <20070329204005.1c3b7130@gumby.homeunix.com> <20070329164106.27389f8a@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Mar 2007 16:41:06 -0400 Gerard Seibert <gerard@seibercom.net> wrote: > On Thu, 29 Mar 2007 20:40:05 +0100 > RW <fbsd06@mlists.homeunix.com> wrote: > > > Portmanager is really no better, the dependencies recorded in the > > package database are also recursive. The big problem with gettext > > was that a lot of port failed to build afterwards, leaving them > > with a missing library. > > I have had problems in the past getting 'portupgrade' to properly > update all of the dependencies required when doing a major update; > i.e., 'gettext'. > > On the other hand, I have never had a problem using 'portmanager' > provided I used the '-p -f' flags. Your missing the point that when portupgrade fails to upgrade the dependent ports, it doesn't really matter because it has preserved copies of the old libraries. That allows software built against the old and new versions to co-exist until the underlying problem is fixed. I use portmanager myself, but no upgrade utility can guarantee that any port will build. I got into this problem myself - I couldn't start KDE. I got out of it by deleting gettext, reinstalling the old version with pkg_add -r, and re-upgrading gettext with portupgrade.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070330020152.4f268b66>