Nix and GHC package database management: automatic vs custom database
The goal is to decide whether to allow Nix to automatically populate the GHC package database from the Nix store or to override it with a custom database location for incremental Haskell builds. Nix creates pure build environments that isolate GHC and its dependencies, placing the package database in the Nix store rather than the usual Cabal or Stack user da
haskell