unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Is it necessary to download the native inputs while installing packages?
Date: Fri, 19 Jan 2018 16:13:17 -0800	[thread overview]
Message-ID: <20180120001317.GD18016@jasmine.lan> (raw)
In-Reply-To: <MWHPR16MB006303E0441F05881D4DF68B92E80@MWHPR16MB0063.namprd16.prod.outlook.com>

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

On Thu, Jan 18, 2018 at 08:54:32PM +0000, Fis Trivial wrote:
> 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. :)

Although native-inputs are typically things that are only required while
building [0], there's nothing that prevents a built package from keeping
references to native-inputs.

[0] The "native" part is related to cross-compilation.

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

  parent reply	other threads:[~2018-01-20  0:13 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
2018-01-19 13:24       ` Ludovic Courtès
2018-01-20  0:13       ` Leo Famulari [this message]
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=20180120001317.GD18016@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ybbs.daans@hotmail.com \
    /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).