From: Ricardo Wurmus <rekado@elephly.net>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 35907@debbugs.gnu.org
Subject: [bug#35907] note
Date: Sat, 01 Jun 2019 06:16:52 +0200 [thread overview]
Message-ID: <87d0jyj5xn.fsf@elephly.net> (raw)
In-Reply-To: <4E64EFA7-EDBA-4C06-A25E-4600CE49B969@vllmrt.net>
Hi Robert,
> Note that I’m not sure it’s actually a good idea to exclude (all of) these packages
> from the dependencies: They’re mostly bundled with ghc because they are used in the
> ghc build. As such, it might well be that future ghc versions switch out e.g.
> “bytestring” for some alternate data structure, which would then require changes to
> all package definitions that currently silently depend on “bytestring”.
While this is correct, we cannot seem to remove them from the
environment when building packages. If we allow these packages to be
added as inputs and these packages are at different versions from what
GHC provides we get into trouble.
This happened in the past, unfortunately, and it’s hard to debug.
> Should I include a patch to remove the explicitly packaged `ghc-text` and other
> packages of this type?
Yes, I think this would be good.
Thank you for working on this!
--
Ricardo
next prev parent reply other threads:[~2019-06-01 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 20:11 [bug#35907] [PATCH] guix import hackage: update list of ghc-included packages Robert Vollmert
2019-05-28 13:39 ` [bug#35907] note Robert Vollmert
2019-06-01 4:16 ` Ricardo Wurmus [this message]
2019-06-01 4:24 ` bug#35907: [PATCH] guix import hackage: update list of ghc-included packages 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
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=87d0jyj5xn.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35907@debbugs.gnu.org \
--cc=rob@vllmrt.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 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).