From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 46800@debbugs.gnu.org
Subject: [bug#46800] [PATCH] Allow defining multiple substituters
Date: Tue, 02 Mar 2021 21:37:36 +0100 [thread overview]
Message-ID: <87o8g1thpr.fsf@gnu.org> (raw)
In-Reply-To: <c9f5535b93c0e0e832017e8f6f4ec3182fdad971.camel@telenet.be> (Maxime Devos's message of "Fri, 26 Feb 2021 18:41:51 +0100")
Hi Maxime,
Maxime Devos <maximedevos@telenet.be> skribis:
> This patch series is my suggestion for allowing
> multiple "substitution methods" or "substituters"
> as I call them. Currently, only a method for HTTP/S
> is defined, though I hope it will be a good basis
> for a common framework for substitutes over GNUnet
> and IPFS.
Thanks for working on this!
As discussed on IRC, the daemon used to have support for multiple
substituters, but as a built-in C++ interface, which I removed in
f6919ebdc6b0ce0286814cc6ab0564b1a4c67f5f.
The Scheme interface you propose is of course nicer :-), but I’m still
not sure it’s necessary. For example, in the IPFS prototype at
<https://issues.guix.gnu.org/33899>, IPFS support goes hand in hand with
HTTP support: narinfos are retrieved over HTTP and nars can be retrieved
over IPFS, or HTTP. Likewise with “digests”:
<https://lists.gnu.org/archive/html/guix-devel/2021-01/msg00080.html>.
Another issue is that it may be that, instead of letting users choose
one method and stick to it, we’d rather let them choose a policy that
can automatically pick the “best” method, dynamically adjusting choices.
All in all, I would prefer to wait until there’s a clear need for this
abstraction.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-03-02 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 17:41 [bug#46800] [PATCH] Allow defining multiple substituters Maxime Devos
2021-03-02 20:37 ` Ludovic Courtès [this message]
2021-03-04 7:48 ` Maxime Devos
2021-03-12 17:37 ` Ludovic Courtès
2021-03-05 20:05 ` Maxime Devos
2021-06-06 17:52 ` Tony Olagbaiye
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8g1thpr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=46800@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).