@@ -4,8 +4,8 @@ your Haskell package dependencies, but also the required system
4libraries and build tools.
4libraries and build tools.
6Inside the development shell, you can run commands such as `ghc`,
6Inside the development shell, you can run commands such as `ghc`,
7+`ghci`, or `cabal new‑build` (`cabal build` on Cabal 3.0),
7−`ghci`, or `cabal new‑build`, and they will have all dependencies
8+and they will have all dependencies available.
10Every dependency will be cached in your Nix store. If you have set up
10Every dependency will be cached in your Nix store. If you have set up
11Hydra CI, then your team can share pre-built dependencies.
11Hydra CI, then your team can share pre-built dependencies.
@@ -21,7 +21,8 @@ it exists in a file called `default.nix`.
21 rebuild all dependencies, even though they are available in the
21 rebuild all dependencies, even though they are available in the
22 shell. However, if you have a Stack project, you can generate the
22 shell. However, if you have a Stack project, you can generate the
23 package set with Haskell.nix, then use `cabal new‑build` to work
23 package set with Haskell.nix, then use `cabal new‑build` to work
24− on it.
24+ on it. Starting Cabal 3.0 `cabal build` will work out of the box, as
25+ new style builds are the default.
26## How to get a development shell for a package
27## How to get a development shell for a package