From: ludo@gnu.org (Ludovic Courtès)
To: "Rémi Birot-Delrue" <asgeir@free.fr>
Cc: guix-devel@gnu.org, gnunet-developer@gnu.org
Subject: Re: [GSoC] Guix + GNUnet: what’s next
Date: Thu, 02 Jul 2015 14:33:20 +0200 [thread overview]
Message-ID: <87ioa2d9in.fsf@gnu.org> (raw)
In-Reply-To: <87vbe23j59.fsf@free.fr> ("Rémi Birot-Delrue"'s message of "Thu, 02 Jul 2015 13:15:30 +0200")
Hi Rémi,
Thanks for the update!
So I can see two milestones now, as we discussed before:
1. Create a variant of ‘guix publish’ that publishes over GNUnet’s
file sharing (FS) service, using the neat bindings that you wrote.
For that you can literally copy guix/scripts/publish.scm as a
starting point, and simply remove the HTTP-related code (which is a
small fraction.) The rest will be mostly identical: narinfo
meta-data generation, signing. I guess it will be easy to test it
using gnunet-search and similar tools.
As a 2nd step, we’ll see how we can refactor things to allow code
sharing between the existing ‘guix publish’ and its GNUnet variant.
2. Create a variant of ‘guix substitute’ for searches through GNUnet.
Again, a large part of the code is about narinfo and signature
checking, and it can be reused.
I’m not completely clear on how search for substitutes will work,
though. Currently, when the user wants to build /gnu/store/xyz, ‘guix
substitute’ simply fetches http://hydra.gnu.org/xyz.narinfo. How will
that work with GNUnet? Are we going to look up their /gnu/store file
name?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-07-02 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 11:15 [GSoC] Guix + GNUnet: what’s next Rémi Birot-Delrue
2015-07-02 12:33 ` Ludovic Courtès [this message]
2015-07-02 16:49 ` Rémi Birot-Delrue
2015-07-02 20:32 ` Ludovic Courtès
2015-07-02 21:58 ` [OSM-dev] [GNUnet-developers] " Daniel Golle
2015-07-02 22:56 ` Paul Norman
2015-07-03 2:02 ` [OSM-dev] " Daniel Golle
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=87ioa2d9in.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=asgeir@free.fr \
--cc=gnunet-developer@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.