Re: package dependencies

[Pjotr Prins <pjotr.public12@thebird.nl>]

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
> 

--