From: Lars-Dominik Braun <lars@6xq.net>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Saku Laesvuori <saku@laesvuori.fi>, help-guix@gnu.org
Subject: Re: GHC packages' inputs leak in guix shell
Date: Tue, 29 Aug 2023 09:12:09 +0200 [thread overview]
Message-ID: <ZO2aSQxzFylfSKAt@philomena> (raw)
In-Reply-To: <874jkjqtsx.fsf@gmail.com>
Hi Simon,
> Right? Well, I do not know if it is possible. I guess it is because of
> this file:
>
> --8<---------------cut here---------------start------------->8---
> $ find $(guix build ghc-esqueleto) -type f -print | grep base64
> /gnu/store/zqax59v1v537h26g0kypka6klaaahnqf-ghc-esqueleto-3.5.8.1/lib/ghc-9.2.5/ghc-esqueleto-3.5.8.1.conf.d/base64-bytestring-1.2.1.0-CQYLTs5ShsEFl2lwe4hRrI.conf
> --8<---------------cut here---------------end--------------->8---
>
> Lars, WDYT?
your analysis is correct, but due to the nature of how Haskell builds work
we cannot remove that file (because anything depending on ghc-esqueleto
would not build any more) or relocate it to a different output (because
that would cause a cycle).
I can’t check right now, but I’m guessing a plain `cabal install`
would also add base64-bytestring to GHC’s visible packages?
Cheers,
Lars
next prev parent reply other threads:[~2023-08-29 7:13 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 [this message]
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=ZO2aSQxzFylfSKAt@philomena \
--to=lars@6xq.net \
--cc=help-guix@gnu.org \
--cc=saku@laesvuori.fi \
--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).