Date: Sun, 23 Apr 2023 15:01:02 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: "Piotr P. Stefaniak" <pstef@freebsd.org> Cc: Colin Percival <cperciva@freebsd.org>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: df53ae0fdd98 - main - Remove portsnap(8) Message-ID: <ZEVILm8lQqpR5TmP@FreeBSD.org> In-Reply-To: <ZETMQtuwit%2Bc/0MW@freefall.freebsd.org> References: <202304230112.33N1ChPx076100@gitrepo.freebsd.org> <ZETMQtuwit%2Bc/0MW@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 23, 2023 at 06:12:18AM +0000, Piotr P. Stefaniak wrote: > On 2023-04-23 01:12:43, Colin Percival wrote: > > Remove portsnap(8) > > > > Rather than having a tool in the FreeBSD base system for obtaining > > the FreeBSD ports tree, users are encouraged to `pkg install git` > > and then `git clone https://git.FreeBSD.org/ports.git /usr/ports`. > > With my 64 KB/s downlink a shallow copy of just the main branch takes > almost 4 hours. What's worse, git has no way of resuming an interrupted > download. My internet connection is roughly the same, and full "git clone" always fails. However, repeated "git fetch --depth=n ; n++" allowed me to get the ports tree in a few days, eventually. I have to use this trick for any large repo, it migth seem annoying, but it does work. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZEVILm8lQqpR5TmP>