From: Federico Beffa <beffa@ieee.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: propagating inputs in ghc-* packages
Date: Sun, 2 Oct 2016 17:42:54 +0200 [thread overview]
Message-ID: <CAKrPhPMN40BESFRVJHKqQEmVJX9vmw+vjRm1Ng0YG4zm5iafHw@mail.gmail.com> (raw)
In-Reply-To: <87twcv8jou.fsf@elephly.net>
On Sun, Oct 2, 2016 at 6:21 AM, Ricardo Wurmus <rekado@elephly.net> wrote:
>> That sounds great! Just to be sure: you are saying that if you install
>> any library (call it A) and the GHC compiler into your profile then you
>> are able to compile your program (making use of library A) without
>> also having to manually install any input of library A?
>
> This seems to be the case. Here is an example ghci session in which I’m
> using “ghc-pandoc” as a library without having to install any of the
> numerous inputs to “ghc-pandoc” (and their inputs):
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ./pre-inst-env guix environment --ad-hoc ghc ghc-pandoc
> […]
> rekado in guix-wip [env]: ghci
> GHCi, version 7.10.2: http://www.haskell.org/ghc/ :? for help
> Prelude> import Text.Pandoc
> Prelude Text.Pandoc> readMarkdown def "Hello"
> Right (Pandoc (Meta {unMeta = fromList []}) [Para [Str "Hello"]])
> Prelude Text.Pandoc> :q
> Leaving GHCi.
> rekado in guix-wip [env]:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Nice. Thanks for checking.
next prev parent reply other threads:[~2016-10-02 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 21:07 propagating inputs in ghc-* packages Federico Beffa
2016-10-01 7:45 ` Ricardo Wurmus
2016-10-01 9:14 ` Federico Beffa
2016-10-02 4:21 ` Ricardo Wurmus
2016-10-02 15:42 ` Federico Beffa [this message]
2016-10-01 16:31 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2016-09-30 9:24 Ricardo Wurmus
2016-09-30 14:37 ` Eric Bavier
2016-10-02 11:59 ` Ricardo Wurmus
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=CAKrPhPMN40BESFRVJHKqQEmVJX9vmw+vjRm1Ng0YG4zm5iafHw@mail.gmail.com \
--to=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.