all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Saku Laesvuori <saku@laesvuori.fi>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: GHC packages' inputs leak in guix shell
Date: Thu, 24 Aug 2023 19:16:53 +0300	[thread overview]
Message-ID: <20230824161653.vha6sk7ot34nixpe@X-kone> (raw)
In-Reply-To: <86r0nsztxu.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 750 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.
> 
> What do you mean by “leak”?

I would expect packages to keep their (non-propagated) inputs separate
from the environment I use. Here ghc-esqueleto makes it's haskell inputs
visible to the ghc in my environment.

> Does it happen if you run
> 
>     guix shell -C ghc-esqueleto -D ghc-bytestring-builder
> 
> ?

Yes it does.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-08-24 16:17 UTC|newest]

Thread overview: 9+ 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 [this message]
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
2023-10-04 18:26             ` bug#66347: GHC packages " Simon Tournier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230824161653.vha6sk7ot34nixpe@X-kone \
    --to=saku@laesvuori.fi \
    --cc=help-guix@gnu.org \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.