From: ludo@gnu.org (Ludovic Courtès)
To: Tonton <tonton@riseup.net>
Cc: 31418@debbugs.gnu.org
Subject: [bug#31418] [PATCH 4/6] gnu: Add ghc-binary.
Date: Sun, 13 May 2018 23:13:12 +0200 [thread overview]
Message-ID: <874ljbl0nr.fsf@gnu.org> (raw)
In-Reply-To: <20180511203408.29491-3-tonton@riseup.net> (tonton@riseup.net's message of "Fri, 11 May 2018 22:34:06 +0200")
Hello,
I’ve applied patches 1 to 3 with minor tweaks to the descriptions (so
that they’d be full sentences, for instance), but…
Tonton <tonton@riseup.net> skribis:
> * gnu/packages/haskell.scm (ghc-binary): New variable.
[...]
> + (inputs `(("ghc-bytestring" ,ghc-bytestring-builder)
> + ("ghc-array" ,ghc-array)
> + ("ghc-ghc-prim" ,ghc-primitive)
> + ("ghc-hunit" ,ghc-hunit)
> + ("ghc-quickcheck" ,ghc-quickcheck-2.9)
> + ("ghc-test-framework" ,ghc-test-framework)
> + ("ghc-test-framework-quickcheck2" ,ghc-test-framework-quickcheck2-w-qc-2.9)
… here ‘ghc-test-framework-quickcheck2-w-qc-2.9’ is undefined. Did you
mean to define it in the first patch?
Could you send an updated patch set for what remains?
Thanks in advance,
Ludo’.
next prev parent reply other threads:[~2018-05-13 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 20:34 [bug#31419] [PATCH 2/6] gnu: Add ghc-array Tonton
2018-05-11 20:34 ` [bug#31420] [PATCH 3/6] gnu: Add ghc-containers Tonton
2018-05-11 20:34 ` [bug#31421] [PATCH 4/6] gnu: Add ghc-binary Tonton
2018-05-13 21:13 ` Ludovic Courtès [this message]
2018-05-17 14:18 ` [bug#31418] " Ludovic Courtès
2018-05-11 20:34 ` [bug#31422] [PATCH 5/6] gnu: Add ghc-semigroupoids-5.2.2 Tonton
2018-05-17 19:37 ` [bug#31422] [PATCH 1/2] " Tonton
2018-05-20 20:44 ` bug#31422: " Ludovic Courtès
2018-05-11 20:34 ` [bug#31423] [PATCH 6/6] gnu: Add ghc-bytes Tonton
2018-05-17 19:34 ` [bug#31423] [PATCH 2/2] " Tonton
2018-05-20 20:58 ` bug#31423: " 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=874ljbl0nr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31418@debbugs.gnu.org \
--cc=tonton@riseup.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.