You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cabal freeze writes a freeze file that includes setup.* dependencies, so having a freeze file staged under git requires committing to a single choice of a setup.Cabal version.
haskell.nix uses nix-tools compiled against Cabal 3.10.3.0
Would it be possible to migrate nix-tools to Cabal 3.12, or otherwise lift the restriction and have a way for me to override the Cabal version used in nix-tools?
The text was updated successfully, but these errors were encountered:
I am able to work around this issue by overriding nix-tools for a specific project like so:
pkgs.haskell-nix.cabalProject{inheritcompiler-nix-name;src=...;nix-tools=pkgs.haskell-nix.nix-tools-set{inheritcompiler-nix-name;# Don't build a new GHC (9.10.1) just for thiscabalProjectLocal='' constraints: Cabal ==3.12.1.0 '';};
cabalProjectLocal is not the prettiest, there's probably some better way to do this via modules. And also a better way to override this for the entire pkgs rather than just a single project. (I couldn't figure out how to do either).
We're currently experiencing a combination of unfortunate circumstances:
build-type: Custom
in our dependency closure, meaning they depend onsetup.Cabal
.cabal --enable-multi-repl
requiressetup.Cabal >= 3.12
.cabal freeze
writes a freeze file that includessetup.*
dependencies, so having a freeze file staged under git requires committing to a single choice of asetup.Cabal
version.nix-tools
compiled against Cabal 3.10.3.0setup.Cabal < 3.12
in the plan: Does cabal-3.10 imposesetup.Cabal < 3.12
? haskell/cabal#9917nix-tools
.nix-tools
does not support Cabal 3.12 anywayhaskell.nix/nix-tools/nix-tools/nix-tools.cabal
Lines 18 to 19 in 8d879c1
Would it be possible to migrate
nix-tools
to Cabal 3.12, or otherwise lift the restriction and have a way for me to override the Cabal version used innix-tools
?The text was updated successfully, but these errors were encountered: