From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: man/, lib/portage/package/ebuild/
Date: Sun, 10 Jan 2021 03:24:10 +0000 (UTC) [thread overview]
Message-ID: <1610248963.f04dae7728b558ba10b99d1b4979054825fbb0d6.zmedico@gentoo> (raw)
commit: f04dae7728b558ba10b99d1b4979054825fbb0d6
Author: Daniel M. Weeks <dan <AT> danweeks <DOT> net>
AuthorDate: Wed Jan 6 18:35:37 2021 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sun Jan 10 03:22:43 2021 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=f04dae77
Make digests available to fetch command
This makes it possible for the fetch command to utilize a
protocol/service that identifies files by their hash.
Closes: https://github.com/gentoo/portage/pull/655
Signed-off-by: Daniel M. Weeks <dan <AT> danweeks.net>
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
lib/portage/package/ebuild/fetch.py | 6 ++++++
man/make.conf.5 | 14 +++++++++++++-
2 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/lib/portage/package/ebuild/fetch.py b/lib/portage/package/ebuild/fetch.py
index 7be9d0239..e0fecaf23 100644
--- a/lib/portage/package/ebuild/fetch.py
+++ b/lib/portage/package/ebuild/fetch.py
@@ -1291,6 +1291,12 @@ def fetch(myuris, mysettings, listonly=0, fetchonly=0,
"FILE": os.path.basename(download_path)
}
+ try:
+ variables['DIGESTS'] = " ".join(["%s:%s" % (k.lower(), v)
+ for k, v in mydigests[myfile].items() if k != 'size'])
+ except KeyError:
+ pass
+
for k in ("DISTDIR", "PORTAGE_SSH_OPTS"):
v = mysettings.get(k)
if v is not None:
diff --git a/man/make.conf.5 b/man/make.conf.5
index 494d5a212..f6eae6f60 100644
--- a/man/make.conf.5
+++ b/man/make.conf.5
@@ -1,4 +1,4 @@
-.TH "MAKE.CONF" "5" "Sep 2020" "Portage VERSION" "Portage"
+.TH "MAKE.CONF" "5" "Jan 2021" "Portage VERSION" "Portage"
.SH "NAME"
make.conf \- custom settings for Portage
.SH "SYNOPSIS"
@@ -746,6 +746,18 @@ the internet. It must contain the full path to the executable as well as the
place\-holders \\${DISTDIR}, \\${FILE} and \\${URI}. The command should be
written to place the fetched file at \\${DISTDIR}/\\${FILE}.
Also see \fBRESUMECOMMAND\fR.
+.RS
+.TP
+.B Optional FETCHCOMMAND Placeholders
+.TS
+l l l
+___
+l l l.
+Placeholder Meaning Example
+
+\\${DIGESTS} Space separated list of file digests blake2b <hexdigest> sha512 <hexdigest>
+.TE
+.RE
.TP
.B FFLAGS FCFLAGS
Use these variables to set the desired optimization/CPU instruction settings
next reply other threads:[~2021-01-10 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 3:24 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-08 0:47 [gentoo-commits] proj/portage:master commit in: man/, lib/portage/package/ebuild/ Zac Medico
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=1610248963.f04dae7728b558ba10b99d1b4979054825fbb0d6.zmedico@gentoo \
--to=zmedico@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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