Date: Sun, 30 Oct 2005 20:50:26 -0500 From: John DeStefano <john.destefano@gmail.com> To: "Andrew P." <infofarmer@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade stale dependencies Message-ID: <f2160e0d0510301750p160696a8r3b20d07ac903a340@mail.gmail.com> In-Reply-To: <cb5206420510290423v4a107a5dl574ba5387a3424f2@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> <cb5206420510290423v4a107a5dl574ba5387a3424f2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/29/05, Andrew P. <infofarmer@gmail.com> wrote: > 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. If I were to continue to use portsnap, which arguments can I safely add to /etc/crontab? I know "portsnap cron" should be safe, but if I want to completely automate the update process (not for installing packages, but for keeping the ports tree, database, and indexes current), should I also add an entry for "portsnap update" and "portsdb -uUF"? > > 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). > Would you also recommend cron entries for these two commands? I used to use a cron job to run cvsup, and I'd like to implement a better, more complete automated solution, so I don't tangle up my system's packages and dependencies again.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f2160e0d0510301750p160696a8r3b20d07ac903a340>