Understand how Cabal resolves dependencies. To understand how Haskell.nix resolves dependencies, we have to first Will focus only on using Haskell.nix for cabal projects. Haskell.nix also provides other mode of Haskell development in Nix, This would help us understand why certain limitations are present It is important to understand how Haskell.nix works internally. Nevertheless, Cabal offers a wide range of features, some of whichĪre not currently well supported by Haskell.nix. It can usually work out of the box for existing cabal-based Haskell Since Haskell.nix uses cabal-install for the actual package management, Resolve the dependency graph, and converting it into Nix expressions. It does so by making use of cabal-install to Haskell.nix takes multi-versioned approach toward managing Haskell If a solution exists, cabal can automatically generate a Requirements of our dependencies to cabal by specifying versionīounds. Multi-versioned Haskell packages in mind. In comparison, package managers like cabal-install are built with Resolve the new set of dependency versions based on custom requirements. Manual intervention, because there is no mechanism to automatically When version conflicts happen, it often require Provided by nixpkgs do not always provide the exact versions of Haskell As we seens in the previous chapters, the mono-versioned Haskell packages

Haskell packages windowmanager