Date: 04 Feb 2006 16:12:29 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Nikolas Britton <nikolas.britton@gmail.com> Cc: Xn Nooby <xnooby@gmail.com>, freebsd-questions@freebsd.org Subject: Re: Why does portsdb -Uu run so long? Message-ID: <44u0bevneq.fsf@be-well.ilk.org> In-Reply-To: <ef10de9a0602040814q2931457dg206664b6baa46fac@mail.gmail.com> References: <bdf25fde0602010241i30ed79c9x2818c3fa35abf731@mail.gmail.com> <ef10de9a0602032110g5ff97760tb6ead7a638c1ed86@mail.gmail.com> <bdf25fde0602032318u7e01d789u58fe877c25e574cd@mail.gmail.com> <ef10de9a0602040814q2931457dg206664b6baa46fac@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Nikolas Britton <nikolas.britton@gmail.com> writes: > No, If I remember right (someone step in if I'm wrong) make fetchindex > is what you would get if you ran portsdb -Uu. Assuming nothing has been checked in between (1) the building of the index on the server (which you get from fetchindex), and (2) the last snapshot of the ports tree that your cvsup server has taken. In general, these will not be exactly the same, but close enough that the difference hardly ever matters.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44u0bevneq.fsf>