Hi,
With old Haskell setup we'd essentially have a shell.nix that was a bit like
let
pkgs = import {}
some_stuff = …;
in some_stuff.callPackage ./. {};
or some variation thereof. This allowed us to both nix-shell *and*
nix-build shell.nix out of the box. But with haskell-ng we end up with
Hi Mateusz,
> Is there any way to recover old behaviour? I imagine if we can tell if
> we're entering a nix-shell or
> not then we can switch inside the expr and use .env when appropriate but
> I don't know how to achieve this.
>
I have this PR: https://github.com/NixOS/nixpkgs/pull/6307 which wou
Hi Mateusz,
> With old Haskell setup we'd essentially have a shell.nix that was a bit like
>
> let
> pkgs = import {}
> some_stuff = …;
> in some_stuff.callPackage ./. {};
>
> or some variation thereof. This allowed us to both nix-shell *and*
> nix-build shell.nix out of the box. But
I now understand why we don't neccesarily want to use the with-packages
wrapper for building (Peter wrote a nice detailed response to the PR, if
anyone is interested in the reasons).
I am now wondering, why don't we make the `.env` shellHook the default
shellHook for the derivation too? I guess th
Hi Benno,
> Why don't we make the `.env` shellHook the default shellHook for the
> derivation too?
Mateusz requested something like that earlier, and I created [1] to make
sure it's not forgotten. Basically, the idea was that an appropriate
shellHook allows you to work interactively in the stan
