@ncfavier Maybe you could be more specific in what you're trying to do and what is failing?

Here's an example of using a development shell for a Haskell package:

$ nix develop .#haskellPackages.termonad.env
$ nix-shell -I nixpkgs=./. -p cabal-install
$ cabal get termonad-4.2.0.1
$ cd termonad-4.2.0.1/
$ cabal build

This works for me (and Termonad is somewhat of a complicated package to build, since it needs many system dependencies).

A couple things to note here:

When jumping into a development shell for a Haskell package, you'll likely want to use haskellPackages.foo.env, not haskellPackages.foo.
The development environment for a Haskell package doesn't pull in cabal-install, because cabal-install isn't a required dependency. You can build Haskell packages without cabal-install. Also, cabal-install is one of those Haskell dev tools that generally works with multiple compiler versions, so it is often safe to install cabal-install globally.
In practice, almost no one uses haskellPackages.foo.env, but instead functions like haskellPackages.developPackage or haskellPackages.shellFor.

Uh oh!

Haskell development shells are not very useful #196753

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions