Re: [PATCH] Add python2-seqmagick.

[Pjotr Prins]

This contains the most lucid description of 'inputs' I have yet seen.
Could they go into the main Guix documentation?

Pj.

On Sat, Sep 19, 2015 at 07:36:17PM +1000, Ben Woodcroft wrote:
>    On 18/09/15 01:51, Ricardo Wurmus wrote:
> 
>  Hi Ben,
> 
>  thank you very much for your patch!
> 
>    and you sir, for the review.
> 
>  +    (inputs
>  +     `(("python-setuptools" ,python2-setuptools)
> 
>  I think this should be a native input instead.
> 
>    ok
> 
>  +       ("python-biopython" ,python2-biopython)))
> 
>  And this looks like it should be a propagated input instead.  Have you
>  tried running seqmagick after installing it with this package recipe?  I
>  found that Python executables often require either propagated inputs or
>  wrapping in PYTHONPATH to work without runtime errors.
> 
>    I did, although not well enough to pick up the error you point out.
>    Actually I'm a bit confused as to the difference between the input types
>    even after reading the manual. Is this a fair summary?
> 
>    native-inputs: required for building but not runtime - installing a
>    package through a substitute won't install these inputs
>    inputs: installed in the store but not in the profile, as well as being
>    present at build time
>    propagated-inputs: installed in the store and in the profile, as well as
>    being present at build time
> 
>    Anyway, it seems as if the package would have worked because a wrapper is
>    generated with PYTHONPATH including inputs, propagated-inputs and
>    native-inputs. But this seems a bit strange - why would native inputs be
>    in the runtime wrapper?
>    $ cat /tmp/a.fa
>    >a