Date: Sun, 23 Jan 2005 09:18:48 -0800 From: "Michael C. Shultz" <reso3w83@verizon.net> To: freebsd-questions@freebsd.org Cc: Trey Sizemore <trey@fastmail.fm> Subject: Re: KDE issues after recent portupgrade Message-ID: <200501230918.50191.reso3w83@verizon.net> In-Reply-To: <1106499211.61888.7.camel@localhost> References: <1106443760.1123.7.camel@localhost> <200501230841.10791.reso3w83@verizon.net> <1106499211.61888.7.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501230918.50191.reso3w83>