From: Ben Sturmfels <ben@sturm.com.au>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Naming of native-inputs/inputs/propagated-inputs
Date: Tue, 23 Jul 2019 20:36:00 +1000 [thread overview]
Message-ID: <8736ix2g33.fsf@sturm.com.au> (raw)
In-Reply-To: <878sspcahm.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Tue, 23 Jul 2019, Ricardo Wurmus wrote:
> The difference between “native-inputs” and “inputs” is not about whether
> they are needed at build time or runtime. The difference only really
> comes into play when cross-building. “native-inputs” must be of the
> host architecture, while “inputs” are for the target architecture.
>
> It is correct that “native-inputs” often happen to be only used during
> the build, but that doesn’t need to be the case.
>
> Ultimately, runtime inputs are determined by whether they are referenced
> in the output. This is orthogonal to whether they are listed in the
> “native-inputs”, “inputs”, or even “propagated-inputs” field.
Thanks for the clarification Ricardo!
Regards,
Ben
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-07-23 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 5:56 Naming of native-inputs/inputs/propagated-inputs Ben Sturmfels
2019-07-23 10:26 ` Ricardo Wurmus
2019-07-23 10:36 ` Ben Sturmfels [this message]
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=8736ix2g33.fsf@sturm.com.au \
--to=ben@sturm.com.au \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).