From: Tonton <tonton@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Controling requirements when packaging haskell modules
Date: Mon, 14 May 2018 14:11:57 +0200 [thread overview]
Message-ID: <20180514141157.7edcec6e@merlin.browniehive.net> (raw)
In-Reply-To: <87y3gmlbzj.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Mon, 14 May 2018 13:20:48 +0200
Ricardo Wurmus <rekado@elephly.net> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>
> >> You should not package ghc-array, ghc-containers, or ghc-binary — these
> >> are all provided by GHC itself. It is possible that there are some more
> >> packages for which this applies (possibly including semigroupoids).
> >
> > Oops, I pushed ghc-array and ghc-containers just yesterday. Should I
> > revert?
>
> Yes, these packages better should not exist. You can revert the commits
> adding them and modify the package definitions of whatever new packages
> refer to them.
>
> We removed them some time ago when we cleaned up and updated most of the
> Haskell packages.
>
> --
> Ricardo
>
>
Hi, I saw this message yesterday and thought I'd change and fix my patches,
but had other things at that time. I should have sent a short message to the
bug containing the patches.
I'm going to clean up and send new patches without the ghc-array and so on.
(I tested several of the requirements/dependencies and I think I isolated
what needs to be declared).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-14 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 18:22 Controling requirements when packaging haskell modules Ton
2018-05-12 13:54 ` Ricardo Wurmus
2018-05-14 9:26 ` Ludovic Courtès
2018-05-14 11:20 ` Ricardo Wurmus
2018-05-14 12:11 ` Tonton [this message]
2018-05-17 14:18 ` Ludovic Courtès
2018-05-17 18:08 ` Tonton
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=20180514141157.7edcec6e@merlin.browniehive.net \
--to=tonton@riseup.net \
--cc=help-guix@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.
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).