Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Nov 2005 00:20:29 +0300
From:      "Andrew P." <infofarmer@gmail.com>
To:        Colin Percival <cperciva@freebsd.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: cvsup vs. portsnap (was Re: cvsup problem)
Message-ID:  <cb5206420511101320ue1715acw988bba61904de535@mail.gmail.com>
In-Reply-To: <4373AC67.4010403@freebsd.org>
References:  <CA513920FC73A14B964AB258D77EA8D60B559A@mx1.masongeneral.com> <200511091224.13143.kirk@strauser.com> <200511091044.04253.kstewart@owt.com> <200511091313.50741.kirk@strauser.com> <43725078.6000303@freebsd.org> <cb5206420511100647h5fbc1946n88f3fac1e449e758@mail.gmail.com> <4373AC67.4010403@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/10/05, Colin Percival <cperciva@freebsd.org> wrote:
> Andrew P. wrote:
> > There are a couple more points against portsnap:
> > - it lags behind by a few hours.
>
> This is true (well, 1-2 hours).  However, the reason for this
> is that portsnap builds ports INDEX files, and since portsnap
> is usually more up-to-date than the INDEX files fetched by
> "make fetchindex", the lag time is probably less of a problem
> than one might imagine at first.
>
> That said, the build times should be improving somewhat as I
> move portsnap builds to some new hardware in the near future.
>
> > - setting up a mirror is still undocumented
>
> I'm working on it; but for most users, a caching HTTP proxy
> will be far better than an actual portsnap mirror.
>
> Colin Percival
>

satbsd# date
Fri Nov 11 00:11:04 MSK 2005
satbsd# portsnap fetch
Fetching snapshot tag... done.
Fetching snapshot metadata... done.
Updating from Thu Nov 10 02:28:12 MSK 2005 to Thu Nov 10 21:14:57 MSK 2005.
Fetching 4 metadata patches... done.
...

That's 3 hours, and I often see more. But that doesn't
really matter (as in "really really"). Portsnap still would
have saved many lives even if it lagged by a week, and
I think that some humble hardware donation just might
solve the problem by cutting down even those 3 hours.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420511101320ue1715acw988bba61904de535>