From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Fabian Harfert <fhmgufs@web.de>
Cc: guix-devel@gnu.org
Subject: Re: package dependencies
Date: Thu, 10 Dec 2015 05:55:30 +0100 [thread overview]
Message-ID: <20151210045530.GA28215@thebird.nl> (raw)
In-Reply-To: <20151209201329.20594c2e@weiserose.weiserose.de>
Hi Fabian,
It has been noted before that these are not well explained in the docs. I like this
description:
1. *native-inputs*: required for building but not runtime - installing a
package through a substitute won't install these inputs
2. *inputs*: installed in the store but not in the profile, as well as being
present at build time
3. *propagated-inputs*: installed in the store and in the profile, as
well as being present at build time
(I proposed to update the docs at some point, in fact, but I realise
that some people may like the existing description better. Guile/Guix
are documented in a pretty consistent way).
You may also find information on https://github.com/pjotrp/guix-notes/
to be useful. That is basically where I jot down stuff I otherwise
would forget.
Pj.
On Wed, Dec 09, 2015 at 08:13:29PM +0100, Fabian Harfert wrote:
> Hello,
>
> at the moment I am making my first steps in packaging for guix. I would
> like to know, how to define the dependences for a package correctly.
>
> I see three fields in the documentation: "inputs", "native-inputs" and
> "propagated" inputs. Am I right if I say that "native-inputs" stands
> for build dependences and "inputs" is for runtime dependences?
>
> In general I find the guix documentation very clear and useful - and
> I have to say: guix is the best package manager I have met until now.
>
> Fabian
>
--
next prev parent reply other threads:[~2015-12-10 4:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 17:29 [PATCH] doc: rephrase code of conduct Alex Sassmannshausen
2015-12-09 19:13 ` package dependencies Fabian Harfert
2015-12-10 4:55 ` Pjotr Prins [this message]
2015-12-13 13:45 ` Ludovic Courtès
2015-12-14 6:29 ` Pjotr Prins
2015-12-14 8:58 ` Ludovic Courtès
2015-12-14 9:28 ` Pjotr Prins
2015-12-14 16:47 ` Ludovic Courtès
2015-12-14 19:36 ` Leo Famulari
2015-12-15 10:18 ` Pjotr Prins
2015-12-15 10:57 ` Ludovic Courtès
2015-12-16 4:53 ` Packagers tutorial, deployment tutorial Pjotr Prins
2015-12-17 13:01 ` Ludovic Courtès
2015-12-17 18:40 ` Pjotr Prins
2015-12-17 22:09 ` Ludovic Courtès
2015-12-17 22:58 ` Christopher Allan Webber
2015-12-18 1:03 ` Leo Famulari
2015-12-18 1:40 ` Christopher Allan Webber
2015-12-18 3:53 ` Pjotr Prins
2015-12-18 16:58 ` Christopher Allan Webber
2015-12-14 7:03 ` package dependencies Leo Famulari
2015-12-14 7:37 ` Ben Woodcroft
2015-12-14 8:56 ` Ludovic Courtès
2015-12-15 12:57 ` Ludovic Courtès
2015-12-09 21:19 ` [PATCH] doc: rephrase code of conduct Ludovic Courtès
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=20151210045530.GA28215@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=fhmgufs@web.de \
--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 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.