KDE issues after recent portupgrade

[Michael C. Shultz]

On Sunday 23 January 2005 08:53 am, Trey Sizemore wrote:
> On Sun, 2005-01-23 at 08:41 -0800, Michael C. Shultz wrote:
> > Yes. portupgrade screws up the port registration files when you run
> > pkgdb -F.  These are the files in /var/db/pkg/{portname}/+CONTENTS
> >
> > Portmanager does not mess with the registration files and can
> > usually straighten out the damage caused by pkgdb -F. As
> > portmanager runs it gives you good feedback on what it is doing and
> > why, and if you disagree or just question something it is perfectly
> > safe to ctrl-C out
> > of it.  When start again and it will just pick up from when you
> > left off.
>
> So as a general rule, it appears I would just cvsup my ports as usual
> and then use 'portmanager -u' rather than 'portupgrade -arR'.  No
> more need for portsdb -u and pkgdb -F then?

Correct.

-Mike