From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --sync keeps failing
Date: Tue, 03 Aug 2021 11:51:59 +0100 [thread overview]
Message-ID: <3382330.iIbC2pHGDl@lenovo.localdomain> (raw)
In-Reply-To: <20210803114923.7d34e1aa@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On Tuesday, 3 August 2021 11:49:23 BST Neil Bothwick wrote:
> On Tue, 03 Aug 2021 09:55:46 +0100, Michael wrote:
> > Anyhow, I recall using git to sync a live ebuild -9999 from some repo
> > and portage started downloading gigabytes of cruft. Presumably whole
> > decades of old commits I didn't need or have space for. I subsequently
> > discovered I had to set "EGIT_CLONE_TYPE=shallow" in make.conf, but I
> > can't find this variable in the man page now. I suppose/hope portage
> > using git will only download more recent commits?
>
> It does, you get just the current state of the tree by default, it's just
> orders of magnitude faster, even compared with using rsync with a local
> mirror. And I don't have to worry abut syncing too often and upsetting
> infra as I'm syncing from github.
I see, thanks Neil. Does it now check sigs of downloaded data, like rsync
does?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-08-03 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 15:32 [gentoo-user] emerge --sync keeps failing n952162
2021-08-01 18:32 ` Michael Orlitzky
2021-08-02 7:20 ` n952162
2021-08-02 8:08 ` n952162
2021-08-02 11:02 ` Michael Orlitzky
2021-08-02 11:10 ` n952162
2021-08-02 12:01 ` Michael
2021-08-02 13:23 ` Dale
2021-08-02 15:43 ` n952162
2021-08-02 21:17 ` Neil Bothwick
2021-08-02 22:42 ` Michael
2021-08-03 1:28 ` John Covici
2021-08-03 8:55 ` Michael
2021-08-03 10:49 ` Neil Bothwick
2021-08-03 10:51 ` Michael [this message]
2021-09-06 13:55 ` n952162
2021-08-04 13:19 ` Michael Orlitzky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3382330.iIbC2pHGDl@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox