| 22 Oct 2024 |
 maralorn | In reply to @b:chreekat.net
I rather doubt it. There used to be a way to say "just use the packages that come with the compiler", which probably would work, but I think that went away when casa came into the scene Do you know when that was? | 11:41:08 |
 chreekat | Well hm, in the docs it's still listed as possible | 11:41:33 |
| chreekat | https://docs.haskellstack.org/en/stable/configure/yaml/project/#snapshot | 11:41:40 |
| maralorn | I only have this problem because I am on a terribly outdated nixpkgs anyway … | 11:41:40 |
 sterni | In reply to @maralorn:maralorn.de
You wanna do that in the nixpkgs manual? yes | 11:42:18 |
| chreekat | In reply to @maralorn:maralorn.de
Do you know when that was? (I wouldn't know) | 11:43:25 |
| chreekat | can't repro with a later snapshot, interesting | 11:47:43 |
| chreekat | I think I'll leave it at that, then | 11:49:09 |
|  niko ⚡️ changed their profile picture. | 11:49:17 |
| chreekat | Well, if anyone else can try my repro, that would be good. I'm worried about some fucked up artifact being cached in ~/.stack or something. This already happened with one of the stack-built Setup binaries: it was built with references to missing symbols, and I had to delete it and rebuild it in a proper shell | 11:59:07 |
| maralorn | In reply to @maralorn:maralorn.de
Is there an easy way to tell stack to just use all dependencies and ghc from the nix-provided environment and just build my project? Basically ignoring any snapshots? I am shocked by how easy it is. | 14:44:29 |
| maralorn | Does anyone know if there is a way to only build the haddocks with our builder? | 15:42:05 |
| 23 Oct 2024 |
 cdepillabout | In reply to @b:chreekat.net
in that issue, cdepillabout reports a problem while using buildStackProject. It looks different to the main problem of the ticket, so maybe I should open another one? In our case (I have the same set of conditions), the thing getting repeated is -I/foo/bar/baz I have a long-standing issue in one of my projects with this exact problem: https://github.com/cdepillabout/termonad/issues/99 (although I basically just link to the nixpkgs issue as well) | 03:22:24 |
| cdepillabout | I was also never able to figure out exactly what the problem is here, or even where to report the problem, other than what is posted in that nixpkgs issue | 03:23:01 |
| cdepillabout | In reply to @maralorn:maralorn.de
Is there an easy way to tell stack to just use all dependencies and ghc from the nix-provided environment and just build my project? Basically ignoring any snapshots? If I remember correctly, it is even possible to do with snapshots as well, as long as you give stack a ghc with a fully-populated package db with the exact versions (and revisions) of all the packages it is expecting from the snapshot. | 03:25:24 |
| cdepillabout | Although if you're going to go this route, it is generally easier for us to just use cabal-install instead. | 03:25:49 |
| cdepillabout | In reply to @b:chreekat.net
Well, if anyone else can try my repro, that would be good. I'm worried about some fucked up artifact being cached in ~/.stack or something. This already happened with one of the stack-built Setup binaries: it was built with references to missing symbols, and I had to delete it and rebuild it in a proper shell This happens quite frequently if you're using Stack with Nix. You can get your ~/.stack into a bad state if you have a bunch of projects all using stack with the same resolver, but all using widely different Nixpkgs checkouts. Your Haskell libraries end up getting linked to different system library versions, and stack doesn't know how to deal with this. | 03:28:13 |
| chreekat | In reply to @cdepillabout:matrix.org
This happens quite frequently if you're using Stack with Nix. You can get your ~/.stack into a bad state if you have a bunch of projects all using stack with the same resolver, but all using widely different Nixpkgs checkouts. Your Haskell libraries end up getting linked to different system library versions, and stack doesn't know how to deal with this. Aha. Does cabal not have the same problem? | 04:28:04 |
| cdepillabout | Cabal does have the same problem. However, when people use cabal with Nix, it is pretty uncommon to let cabal build dependencies. Most people end up giving cabal a Nix-built package db. So most people don't end up with anything under ~/.cabal/store. So you rarely see people complaining about this in practice. | 06:23:20 |
 Alex | I imagine that similar things can happen with Cabal's dist-newstyle though? | 06:33:26 |
| chreekat | big yikes | 07:34:29 |
| cdepillabout | Yeah, I imagine that's true. Although my guess is that developers are much more comfortable with doing cabal clean or stack clean to delete local build caches (dist-newstyle and .stack-work) when faced with strange linking errors. It takes a little bit more of a leap to realize you also have to clean out ~/.cabal/store and ~/.stack. | 08:30:02 |
| maralorn | cdepillabout: Is there a trick to get stack to not put .stack-work somewhere where it gets copied into the nix-store when I build the package with Nix? | 08:50:51 |
 @luna-null:matrix.org | So uh... how do I get haskell to work on nixos? I can get ghci to work but then I can't get some libraries to work | 09:47:09 |
| @luna-null:matrix.org | Specifically trying to get Text.Pretty.Simple.pPrint and System.Random; seems like they won't work no matter what I do | 09:47:58 |
| @luna-null:matrix.org | And every flake or shell I try to get into seems to run into an error; probably because I'm not using cabal or stack right, but still. I'm very stuck | 09:48:45 |
| @luna-null:matrix.org removed their display name Autumn. | 09:49:26 |
| chreekat | @luna-null:matrix.org: big question. :D What is your use case? A ghci session with the packages you want available? | 09:53:59 |
| chreekat | I'll show how you can do that, but note that it makes for a very different solution that other use cases might use | 09:54:26 |
| @luna-null:matrix.org | For ghci, I want the Text.Pretty.Simple.pPrint library. For System.Random, I want it for a program I made that used to work but doesn't anymore since switching to nixos | 09:55:19 |
