-
Notifications
You must be signed in to change notification settings - Fork 248
Add tool
documentation
#1917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
How can I use a pre-release version of Cabal? In particular, I'd like to use 3.10.3.0 (which is not on hackage yet). I am happy to figure out how to download & build from github, but I can't figure out how to tell haskell.nix to use it everywhere. Thanks for any help! |
Instead of setting
|
Oh I missed that bit. Do you need it to be used as the solver and for Setup as well? Is it ok if GHC and its dependencies build with the old Cabal? To replace Cabal used for solving your projects build plan.The solver is now included in nix-tools. It might be a bit tricky, but I think you could pass in the location of the Cabal library as a To replace Cabal used in SetupI think packages with If you can't use Something like:
|
This is great stuff! I think it's close to what I need. I'm trying to compile my code under 9.8.1, and I'm running into issues with plugins:
The fix at haskell/cabal#9384 was merged into
Did you intend I add this overlay when importing nixpkgs (to override
I am using invalid paths for I do get errors when I try to evaluate Thank you for your help so far! |
I've managed to reproduce the problem I'm running into with plugins at #2155. I haven't tried to fix it yet with the above. |
The
tool
andtools
features (haskell-nix.tool(s)
, theshellFor.tools
argument andshell.tools
) are not well covered by the documentation. However there is a comment in the code. We should update the documentation to cover this and also discuss alternatives (usinghaskell-nix.hackage-package
,haskell-nix.hackage-project
andhaskell-nix.cabalPackage
directly).haskell.nix/overlays/tools.nix
Lines 1 to 39 in 3473e3c
The text was updated successfully, but these errors were encountered: