Date: Sat, 29 Oct 2005 15:23:58 +0400 From: "Andrew P." <infofarmer@gmail.com> To: John DeStefano <john.destefano@gmail.com> Cc: Eric F Crist <ecrist@secure-computing.net>, "Michael C. Shultz" <ringworm01@gmail.com>, freebsd-questions@freebsd.org Subject: Re: portupgrade stale dependencies Message-ID: <cb5206420510290423v4a107a5dl574ba5387a3424f2@mail.gmail.com> In-Reply-To: <f2160e0d0510281951s541d3d9ft808d36b023fa9661@mail.gmail.com> References: <f2160e0d0510151746n28cdbb25s2150337c0c6f7cfc@mail.gmail.com> <6FB767AE-D4D7-4C38-90C0-726D48AF5654@secure-computing.net> <f2160e0d0510281731u268c1f75y82ec93a0ed08ad40@mail.gmail.com> <200510281922.16495.ringworm01@gmail.com> <f2160e0d0510281951s541d3d9ft808d36b023fa9661@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/29/05, John DeStefano <john.destefano@gmail.com> wrote: > > Needless to say, this process wasn't much fun. What can I do to keep > this from happening again? What can/can't I safely include in cron to > automate database and index maintenance? > cvsup or portsnap, then portsdb -uUF. Work under any circumstances, leave you with updated ports tree and indexes. You can also try portupgrade -aF (prefetches needed files to speed up manual upgrade at a later time) and portsclean -DP (removes sources and packages which become outdated due to ports tree updates).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420510290423v4a107a5dl574ba5387a3424f2>