angerman changed the topic of #haskell.nix to: https://input-output-hk.github.io/haskell.nix - alternative haskell infrastructure for nix; logs at https://logs.nix.samueldr.com/haskell.nix
proofofkeags has joined #haskell.nix
fendor has joined #haskell.nix
__monty__ has joined #haskell.nix
<shirothe> __monty__: Sorry for just disappearing so suddenly. I've never worked with a real haskell project so I thought I had to clone the libraries in question and reference them somehow in cabal.project. I've gotten it to work now though using allow-newer, thanks!
<__monty__> shirothe: Np, thanks for the reply. Good luck with haskell and nix \o/
<shirothe> I've got another small question though, do I have to explicitly set the version numbers in the tools argument of shellFor?
proofofkeags has quit [Ping timeout: 252 seconds]
<shirothe> The hackage version of basement is not yet compatible with ghc 9 but there's already a commit on the github page. How can I tell the dependency resolver to use the github version? Adding it to cabal.project is not enough (I assume it's because the commit did not bump up the version number?)
<__monty__> A source-repository-package stanza should be enough. Have you tried passing the commit hash as tag? https://cabal.readthedocs.io/en/3.4/cabal-project.html#specifying-packages-from-remote-version-control-locations
<shirothe> yeah I did that but it still tries to compile the latest hackage version. I assume that's because I can't depend on the new version in my .cabal file since I have no way to differentiate it from the latest hackage version. Therefore cabal probably thinks that the hackage version is fine to use
<shirothe> as far as I can tell I would have to either somehow "hide" the hackage version of basement or be able to specify a commit in my .cabal file (but I think you can only specify cabal versions as constraints)
<__monty__> Hmm, no, I think that should be enough. Your cabal.project *does* apply to your package, right?
<__monty__> Maybe try cabal v2-clean then retry v2-build?
<shirothe> well I can't even enter nix-shell since that's when haskell.nix tries to build basement. When I use my global cabal (haven't done that before) it can't resolve the dependencies
<shirothe> probably because my global ghc is still on version 8
<__monty__> Hmm, haskell.nix should rebuild on changes. Maybe your src filter is too strict and not including cabal.project?
<shirothe> If you mean inside of default.nix, I'm simply using: https://www.irccloud.com/pastebin/MIBpMdsF/default.nix
<__monty__> And is your cabal.project checked into git?
<__monty__> I usually prefer cleanSourceHaskell (Though insisting on having things checked in is good practice too.) https://input-output-hk.github.io/haskell.nix/reference/library/#cleansourcehaskell
<shirothe> didn't change anything, using cleanSourceHaskell doesn't make a difference either
proofofkeags has joined #haskell.nix
__monty__ has quit [Quit: leaving]
fendor has quit [Remote host closed the connection]
proofofkeags_ has joined #haskell.nix
proofofkeags has quit [Ping timeout: 240 seconds]