unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fis Trivial <ybbs.daans@hotmail.com>
To: Leo Famulari <leo@famulari.name>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>,
	Tobias Geerinckx-Rice <me@tobias.gr>
Subject: Re: Is it necessary to download the native inputs while installing packages?
Date: Thu, 18 Jan 2018 20:54:32 +0000	[thread overview]
Message-ID: <MWHPR16MB006303E0441F05881D4DF68B92E80@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
In-Reply-To: <DEA98818-2EA9-4CDE-B213-A0893A2693BF@famulari.name>

Sorry about the mess in the original question.

>
> ‘Installing’ is too ambiguous to answer.
>
> - When *substituting* (installing a binary), native-inputs are not
> required and should never be downloaded.

This answers my question in mind, thanks. :)

>
> If any of the substitute servers *can* provide a binary, no
> native-inputs will be downloaded at all.
>
> Why are you adding ‘--fallback’?
>

As you explained, the substituting process failed.

Thanks for explaining things clearly. I will try to look into the source of
guix next time.

  parent reply	other threads:[~2018-01-18 20:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 15:19 Is it necessary to download the native inputs while installing packages? Fis Trivial
2018-01-18 17:36 ` Tobias Geerinckx-Rice
2018-01-18 19:56   ` Leo Famulari
2018-01-18 20:01     ` Tobias Geerinckx-Rice
2018-01-18 20:54     ` Fis Trivial [this message]
2018-01-19 13:24       ` Ludovic Courtès
2018-01-20  0:13       ` Leo Famulari
2018-01-20 10:40         ` Prevent native-inputs references ending up in the final binary Danny Milosavljevic
2018-01-20 15:47           ` Tobias Geerinckx-Rice
2018-01-21 22:37             ` Leo Famulari
2018-01-21 22:47               ` Tobias Geerinckx-Rice
2018-01-24 14:26                 ` Ludovic Courtès
2018-01-26  0:56           ` Fis Trivial
2018-01-26  1:05             ` Tobias Geerinckx-Rice

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=MWHPR16MB006303E0441F05881D4DF68B92E80@MWHPR16MB0063.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=me@tobias.gr \
    /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).