Hi Peter, > The "env" attribute of engine-io (which is > what nix-shell enters here) gives you an environment in which engine-io > can be compiled.
If I remember correctly, old `haskellPackages.mkDerivation` was producing an environment with compiled sources and installed libraries. How to configure `shell.nix` to get `cabal configure && cabal build` done after entering the nix-shell? What was the reason to move this step out of nix-shell routine? On 31 May 2015 at 12:13, Peter Simons <[email protected]> wrote: > Hi Dmitry, > > > After I did `nix-shell` engine-io package is not actually installed > > inside this shell. > > it is not supposed to be. The "env" attribute of engine-io (which is > what nix-shell enters here) gives you an environment in which engine-io > can be compiled. That environment does not contain engine-io. > > Best regards, > Peter > > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
