From: Saku Laesvuori <saku@laesvuori.fi>
To: help-guix@gnu.org
Subject: GHC packages' inputs leak in guix shell
Date: Tue, 15 Aug 2023 09:51:50 +0300 [thread overview]
Message-ID: <20230815065150.5joaxyts646mnpex@X-kone> (raw)
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
Running `guix shell --pure ghc-esqueleto -D ghc-bytestring-builder`
results in an environment that has the base64-bytestring package (from
ghc-base64-bytestring) visible, even though it is not listed on listed
the command line (ghc-bytestring-builder doesn't dependend on it). It
seems to "leak" from the inputs of ghc-esqueleto which does depend on
ghc-base64-bytestring.
Is this a bug in guix or is it unavoidable for some reason?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-08-15 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:51 Saku Laesvuori [this message]
2023-08-24 9:11 ` GHC packages' inputs leak in guix shell Simon Tournier
2023-08-24 16:16 ` Saku Laesvuori
2023-08-28 11:40 ` Simon Tournier
2023-08-28 19:15 ` Saku Laesvuori
2023-08-29 7:12 ` Lars-Dominik Braun
2023-08-29 20:30 ` Saku Laesvuori
2023-09-09 10:05 ` Saku Laesvuori
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=20230815065150.5joaxyts646mnpex@X-kone \
--to=saku@laesvuori.fi \
--cc=help-guix@gnu.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.
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).