From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Using IPFS to host mirrors of source packages
Date: Sat, 12 Aug 2017 15:58:52 +0200 [thread overview]
Message-ID: <20170812135852.GA25655@thebird.nl> (raw)
In-Reply-To: <87inhtykvj.fsf@dustycloud.org>
On Fri, Aug 11, 2017 at 02:17:36PM -0500, Christopher Allan Webber wrote:
> I like the idea... a lot!
>
> Though I think we'll have to address, how do we *get* the packages from
> IPFS? Do we use an http gateway (and whose)? It would be even better
> if by using Guix you automatically could enable contributing to the IPFS
> pool, but I guess that would require a) having an IPFS client in Guile
> and b) having the Nix daemon replaced with Guile to do efficiently.
> (But maybe I'm overthinking it?)
We could start with an https gateway - probably the current guix
distribution server would be a good choice - to share source packages
hosted elsewhere. That would require no coding at all.
Later a Guile ipfs-client added to the daemon can mean that IPFS can
be queried directly. The Python API does not look too complicated:
https://github.com/ipfs/py-ipfs-api/tree/master/ipfsapi
Anyone interested in porting that?
Pj.
--
next prev parent reply other threads:[~2017-08-12 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 15:10 Using IPFS to host mirrors of source packages Pjotr Prins
2017-08-11 15:33 ` Alex Sassmannshausen
2017-08-11 19:17 ` Christopher Allan Webber
2017-08-12 13:58 ` Pjotr Prins [this message]
2017-08-13 7:36 ` Arun Isaac
2017-08-22 8:18 ` Ludovic Courtès
2017-08-22 8:38 ` ng0
2017-08-22 9:14 ` Pjotr Prins
2017-08-22 10:17 ` Ludovic Courtès
2017-08-22 16:49 ` Pjotr Prins
2017-08-22 22:27 ` Ludovic Courtès
2017-08-22 19:31 ` ng0
2017-08-22 9:17 ` ng0
[not found] <mailman.1213.1502464262.21956.guix-devel@gnu.org>
2017-08-11 15:44 ` Joshua Sierles
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=20170812135852.GA25655@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=cwebber@dustycloud.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.