unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix & IPFS
Date: Tue, 16 Oct 2018 14:18:27 +0200	[thread overview]
Message-ID: <20181016121827.77cp2yl4m3dnd322@thebird.nl> (raw)
In-Reply-To: <878t2ygldq.fsf@gnu.org>

On Tue, Oct 16, 2018 at 01:51:29PM +0200, Ludovic Courtès wrote:
> That won’t work: there’s not network access in the build environment in
> order to maximize reproducibility.

IPFS-gx, if I am correct, is just like git for downloading sources. So
we could do gx-fetch in the download phase.

> So I suppose Method #1 is all we have…
> 
> Thoughts?

Nix, these days, has a two phase build. In the second phase you get network
access where you can run network tests. That is kinda interesting.

Pj.

  parent reply	other threads:[~2018-10-16 12:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  7:59 Guix & IPFS Pierre Neidhardt
2018-10-15  8:13 ` Pjotr Prins
2018-10-15  8:20 ` Pjotr Prins
2018-10-15 10:21 ` Ludovic Courtès
2018-10-15 10:40   ` Pierre Neidhardt
2018-10-15 11:35     ` Gábor Boskovits
2018-10-15 11:40       ` Pierre Neidhardt
2018-10-15 14:07         ` Pjotr Prins
2018-10-15 11:56     ` Ludovic Courtès
2018-10-15 12:56       ` Pierre Neidhardt
2018-10-15 13:56         ` Pierre Neidhardt
     [not found]           ` <20181015140856.xd3de5hkumtaueer@thebird.nl>
     [not found]             ` <8736t6jkpu.fsf@ambrevar.xyz>
     [not found]               ` <20181016094752.slvicfgd2rjy57u2@thebird.nl>
     [not found]                 ` <871s8qjjdh.fsf@ambrevar.xyz>
2018-10-16 10:19                   ` Fwd: " Pierre Neidhardt
2018-10-16 11:34                     ` bill-auger
2018-10-16 11:44                       ` Pierre Neidhardt
2018-10-16 11:51           ` Ludovic Courtès
2018-10-16 11:56             ` Pierre Neidhardt
2018-10-16 12:18             ` Pjotr Prins [this message]
2018-10-19 13:45               ` Ludovic Courtès
2018-10-16 16:27     ` Leo Famulari
2018-10-17 17:00       ` Pierre Neidhardt
2018-10-19 13:48         ` Ludovic Courtès
2018-10-19 13:56           ` Pierre Neidhardt
2018-10-23 20:18             ` Pierre Neidhardt
2018-10-24 13:17             ` Ludovic Courtès
2018-10-24 13:58               ` Pierre Neidhardt
2018-10-25 13:34                 ` Ludovic Courtès
2018-10-25 17:40                   ` Pierre Neidhardt
2018-10-25 19:06                     ` Gábor Boskovits
2018-10-25 19:51                       ` Pierre Neidhardt
2018-10-26 17:45                       ` Ludovic Courtès
2018-12-09 20:19                         ` Pierre Neidhardt
2018-12-10  1:52                           ` Pjotr Prins
2018-12-10  8:09                             ` swedebugia
2018-12-10  8:16                               ` Pierre Neidhardt
2018-12-14  9:24 ` Pjotr Prins
2018-12-14  9:30   ` Pierre Neidhardt
2019-09-09 23:19     ` Pjotr Prins

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=20181016121827.77cp2yl4m3dnd322@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).