Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Dec 2002 15:41:58 +0000
From:      Scott Mitchell <>
Subject:   Portupgrade vs. multiple versions of packages
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
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.

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 Mitchell          | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England      | 0x54B171B9 |  don't get sucked into jet engines" | 0xAA775B8B |      -- Anon

To Unsubscribe: send mail to
with "unsubscribe freebsd-questions" in the body of the message

Want to link to this message? Use this URL: <>