From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org
Subject: Re: plz is there a roadmap for a more resilient substitutes infrastructure?
Date: Fri, 2 Nov 2018 22:04:51 +0100 [thread overview]
Message-ID: <20181102210451.htzxk6ox7uldr2fr@thebird.nl> (raw)
In-Reply-To: <87wopv7jzw.fsf@roquette.mug.biscuolo.net>
On Fri, Nov 02, 2018 at 01:16:03PM +0100, Giovanni Biscuolo wrote:
> please is there a roadmap in GNU and/or Guix devel team to address this
> problems?
I think it would be a good idea to create a more distributed approach
for creating and finding substitutes. A simple name service would
help. We could even use IPFS or something to fetch nar files - IPFS
comes with a name service. That way anyone building a substitute could
push it to IPFS and expose it to the rest of the world. Since IPFS is
content-addressable we can prevent injections. Any change to the file
would change its location. So the address + NAR hash is safe. And no
key setting required.
Does away with the dependency on just a few machines. Maintaining
machines is a pain. Why not distribute the effort? I am happy to build
some stuff and put it out there - in fact I already run my own
substitute server, but it has only the substitutes I need. If we all
do that we can bundle resources together. Guix can easily support
that.
If someone wants to think this through and can write a prototype it
would make a great talk at FOSDEM. We can also discuss it at Guix
days.
Pj.
next prev parent reply other threads:[~2018-11-02 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 12:16 plz is there a roadmap for a more resilient substitutes infrastructure? Giovanni Biscuolo
2018-11-02 21:04 ` Pjotr Prins [this message]
2018-11-02 22:51 ` Julien Lepiller
2018-11-03 6:10 ` Pjotr Prins
2018-11-02 21:13 ` Devan Carpenter
2018-11-06 11:23 ` Ludovic Courtès
2018-11-06 11:31 ` Pierre Neidhardt
2018-11-11 18:56 ` Giovanni Biscuolo
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=20181102210451.htzxk6ox7uldr2fr@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.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.
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).