Date: Wed, 01 Jan 2003 15:01:43 +1030 From: Brian Astill <bastill@adam.com.au> To: Scott Mitchell <scott.mitchell@mail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Portupgrade vs. multiple versions of packages Message-ID: <3E126F2F.8030605@adam.com.au> References: <20021231154158.GA22986@fishballoon.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Mitchell wrote:
>Hi all,
>
>I've just spent a fun day upgrading ~180 ports that were about a year out
>of date, which will teach me not to be so lazy in future :-( Anyway,
>portupgrade coped with most of this mess admirably, except for
>(unsurprisingly) the KDE2 --> KDE3 upgrade.
>
That upgrade is a doozie. Been there, done that!
rm -fr qt2 is (I think) the correct thing to do (someone else on the
list will correct me).
Then port kde3.
qt2 and qt3 will NOT live comfortably together. So delete qt2 and all
the apps dependent on it (that includes kde2 and its apps).
The kde3 port will look for the version of qt it needs, fail to find it,
and fetch it for you. Ain't that nice?
Do get confirmation of that rm command I listed, though.
--
Brian
>
>Portupgrade simply refused to upgrade kdelibs-2.2.2 to the latest 3.0.5_1,
>I suspect because the install required some file that portupgrade was
>deinstalling along with the rest of 2.2.2, before it installed 3.0.5. So
>in the end I just installed 3.0.5 on top of the old version, presumably
>leaving various rubbish from the old installation on my system. This
>allowed the rest of the upgrades to proceed happily.
>
>Pkgdb moticed later that I had two kdelibs installed, and helpfully offered
>to deregister one for me. I took it up on this, and ended up with a new
>file +CONTENTS.kdelibs-2.2.2 under /var/db/pkg/kdelibs-3.0.5_1, alongside
>the usual +CONTENTS for the new version.
>
>First question: Will any of the pkg* tools make use of this file so that I
>can, for example, deinstall the new version plus the leftover bits of the
>old version, next time I upgrade?
>
>Second question: If not, is there a nice automated way to find (and remove)
>stray files left behind by old packages that weren't properly removed? I
>could put together a script to find anything in /usr/{local,X11R6} that
>doesn't belong to any installed package, but maybe this wheel has already
>been invented?
>
>Thanks in advance & happy new year,
>
> Scott
>
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E126F2F.8030605>