unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: Paul van der Walt <paul@denknerd.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Question about Haskell packages
Date: Thu, 15 Oct 2015 13:22:38 +0200	[thread overview]
Message-ID: <CAKrPhPNT+T9mS84HP2RPXwJnT7HU52=hh3DFvPyQY01EkZB7nA@mail.gmail.com> (raw)

Paul van der Walt <paul@denknerd.org> writes:

> Hello Guix,
>
> Yesterday i thought to myself that it would be cool to mess around with
> Idris <http://www.idris-lang.org>, on of the dependently-typed
> languages.  Turns out it depends on quite a lot of Hackage packages!  I
> steamed ahead, and now i have packaged all the dependencies.
>
> One weird thing i ran into though, is that frequently, a library L1 will
> build fine, but when you use it as an input to some other library L2,
> the configure phase will fail, saying that L1 is broken, since
> it is missing its dependencies D1..Dn.  Iyzsong suggested on IRC that i
> do like nixpkgs does [0] and simply add all dependencies as
> propagated-inputs.  That should solve that issue, but since i don't 100%
> understand what's going on, i thought it wise to ask you, wise and
> attractive users of Guix, for advice.

The reason is likely that L1 needs one of its input at run time. If
another package declares L1 as its input, but not the library needed by
L1 at run-time, the latter will not be visible in the build environment
(only the declared packages plus some implicit inputs are visible) and
L1 will not be functional. In such a case the library needed at run-time
has to be declared as a propagated-input.

Regards,
Fede

             reply	other threads:[~2015-10-15 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 11:22 Federico Beffa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-15 10:08 Question about Haskell packages Federico Beffa
2015-10-14 15:11 Paul van der Walt
2015-10-14 17:19 ` Taylan Ulrich Bayırlı/Kammer

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='CAKrPhPNT+T9mS84HP2RPXwJnT7HU52=hh3DFvPyQY01EkZB7nA@mail.gmail.com' \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=paul@denknerd.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).