unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Sturmfels <ben@sturm.com.au>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Naming of native-inputs/inputs/propagated-inputs
Date: Tue, 23 Jul 2019 15:56:28 +1000	[thread overview]
Message-ID: <87zhl52t0z.fsf@sturm.com.au> (raw)

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

Hi Folks,

On the rare occasion I dip into Guix packaging, I rely on Pierre's
tutorial[1] because it has the least confusing definition of
"native-inputs" "inputs" and "propagated-inputs". Before that tutorial
existed, I don't think I properly understood the difference.

I know this is superficial, but I wonder if these names could be refined
to better communicate their use. What about:

| Currently         | Possible new name |
|-------------------+-------------------|
| native-inputs     | build-inputs      |
| inputs            | runtime-inputs    |
| propagated-inputs | profile-inputs    |

Just a thought. May even "build-dependencies"? Still doesn't explain
that profile-inputs are also included as build and runtime inputs. Maybe
"build-only-dependencies"?

Regards,
Ben

[1] https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/

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

             reply	other threads:[~2019-07-23  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23  5:56 Ben Sturmfels [this message]
2019-07-23 10:26 ` Naming of native-inputs/inputs/propagated-inputs Ricardo Wurmus
2019-07-23 10:36   ` Ben Sturmfels

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=87zhl52t0z.fsf@sturm.com.au \
    --to=ben@sturm.com.au \
    --cc=guix-devel@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).