Date: Sat, 4 Feb 2006 02:18:43 -0500 From: Xn Nooby <xnooby@gmail.com> To: Nikolas Britton <nikolas.britton@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Why does portsdb -Uu run so long? Message-ID: <bdf25fde0602032318u7e01d789u58fe877c25e574cd@mail.gmail.com> In-Reply-To: <ef10de9a0602032110g5ff97760tb6ead7a638c1ed86@mail.gmail.com> References: <bdf25fde0602010241i30ed79c9x2818c3fa35abf731@mail.gmail.com> <ef10de9a0602032110g5ff97760tb6ead7a638c1ed86@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> It just does, after you cvsup new ports cd into /usr/ports and type > make fetchindex. what way is the "old foolproof way"? > Here is how I update my system (without using a 'make fetchindex') cvsup -g -L 2 /root/stable-supfile less UPDATING make buildworld make buildkernel make installkernel shutdown now cd /usr/src make installworld mergemaster shutdown -r now portsdb -Uu portversion -l "<" portupgrade -arR reboot It takes forever, but it works everytime. Everything else I've ever tried has always had some kind of error, and I never know what they mean or what = I should do. Maybe by never doing a fetchindex, I've never really updated my system, and thats why its never had a problem, lol. That would be embarassing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bdf25fde0602032318u7e01d789u58fe877c25e574cd>