The Haskell ecosystem seems obsessed with NixOS in a way I haven't seen anywhere else.
replyI recall wanting to use Haskell packages that were only available in Nix, but nobody had bothered to make just a normal package.
If you want to create an ecosystem optimized towards correctness, you'll have to curate what you let inside, and drop many things. And Nix is probably the best package manager for correctness.
replyThat of course hurts market share.
There is no correct, only pros and cons. How you weight the pros and cons will not be the same as everyone else.
replyTo be fair, that’s a general problem on NixOS (and other OSes), and one that tools like devenv have tried to solve. You can take what’s included with OS packages, but then you’re stuck with whatever version that is.
reply> You can take what’s included with OS packages, but then you’re stuck with whatever version that is.
replyIt's pretty easy to override things in Nixpkgs though, whether at the system level, or for one application, or just a particular dependency deep in the tree of one script.
Nixpkgs has a bunch of powerful functions to make this easier, e.g. callCabal2nix, makePackageSet, etc.
https://nixos.org/manual/nixpkgs/stable/#haskell-overriding-...
https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...