From: Saku Laesvuori <saku@laesvuori.fi>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Simon Tournier <zimon.toutoune@gmail.com>, help-guix@gnu.org
Subject: Re: GHC packages' inputs leak in guix shell
Date: Tue, 29 Aug 2023 23:30:50 +0300 [thread overview]
Message-ID: <20230829203050.wxtdnalegrwrphrb@X-kone> (raw)
In-Reply-To: <ZO2aSQxzFylfSKAt@philomena>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
> I can’t check right now, but I’m guessing a plain `cabal install`
> would also add base64-bytestring to GHC’s visible packages?
I tested with cabal-install and it somehow manages to hide the haskell
packages that are installed as dependencies.
```
$ guix shell -CN cabal-install coreutils zlib -D ghc-old-time
## Building old-time failed so I added it's inputs.
## Zlib is also required for building the dependency chain.
$ cabal update
$ env -u GHC_PACKAGE_PATH cabal install --lib esqueleto
$ ghci
ﬦ import Database.Esqueleto.Experimental
-- This works, so the package from cabal-install is visible
ﬦ import Data.ByteString.Base64.URL.Lazy
<no location info>: error:
Could not load module `Data.ByteString.Base64.URL.Lazy'
It is a member of the hidden package `base64-bytestring-1.2.1.0'.
You can run `:set -package base64-bytestring' to expose it.
(Note: this unloads all the modules in the current scope.)
```
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-29 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:51 GHC packages' inputs leak in guix shell Saku Laesvuori
2023-08-24 9:11 ` 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 [this message]
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=20230829203050.wxtdnalegrwrphrb@X-kone \
--to=saku@laesvuori.fi \
--cc=help-guix@gnu.org \
--cc=lars@6xq.net \
--cc=zimon.toutoune@gmail.com \
/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).