all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: John Soo <jsoo1@asu.edu>
Cc: help-guix@gnu.org
Subject: Re: Having a problem invoking curl only when using guix pull
Date: Fri, 17 May 2019 03:04:36 +0200	[thread overview]
Message-ID: <87v9y97uxn.fsf@nckx> (raw)
In-Reply-To: <4F8CD8F8-47AF-4C3D-8FD4-95B2ABF40AA6@asu.edu>

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

John,

John Soo wrote:
> Others may correct me if I’m wrong here, but during the build 
> phase, network io is off limits. This is since there is not way 
> to reliably guarantee the contents of things gotten over the 
> network remain unchanged between builds, and so would break the 
> immutability guarantees of the package system. 
>
> Again, I could be wrong, I hope others will correct me. 

You are one hundred percent correct.

The exception to this rule are ‘fixed-output derivations’ such as 
url-fetch, which may fetch whatever they want from anywhere as 
long as the end result matches a provided hash.

These same restrictions do not apply to ‘host-side’ Scheme code, 
however.  One can use the phase of the moon to generate a package 
record.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-05-17  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 22:53 Having a problem invoking curl only when using guix pull Brian Woodcox
2019-05-17  0:21 ` John Soo
2019-05-17  0:31   ` Brian Woodcox
2019-05-17  1:04   ` Tobias Geerinckx-Rice [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-14 22:23 Brian Woodcox
2019-05-16  3:13 ` ison
2019-05-16 21:49 ` Brian Woodcox

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=87v9y97uxn.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=jsoo1@asu.edu \
    /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.