Re: Putting a file into system image ~user/ but not on reconfigure

2023-08-24 Thread Hartmut Goebel

Hi Efraim,

hanks for sharing your thoughts. Meanwhile I learned two things:

 * vagrant needs adjustment to detect and support Guix, which is
   intended by vagrant and vagrant is extensible for this case, see
   https://github.com/hashicorp/vagrant/tree/main/plugins/guests
 * just replacing the "vagran isecure key" in /etc/ssh/auhorizedkeys.d/
   is of not much use: after reboot the file is restored.

So looks like I need to further investigate this topic in more depth.

--
Regards
Hartmut Goebel

| Hartmut Goebel  |h.goe...@crazy-compilers.com|
|www.crazy-compilers.com  | compilers which you thought are impossible |


Re: GHC packages' inputs leak in guix shell

2023-08-24 Thread Saku Laesvuori
> > 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.


signature.asc
Description: PGP signature


Re: GHC packages' inputs leak in guix shell

2023-08-24 Thread Simon Tournier
Hi,

On Tue, 15 Aug 2023 at 09:51, Saku Laesvuori  wrote:
> 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”?

Does it happen if you run

guix shell -C ghc-esqueleto -D ghc-bytestring-builder

?

Cheers,
simon