Sender | Message | Time |
---|---|---|
22 Jul 2025 | ||
Are you sure? Maybe the components are similar enough? I mean they have been compiled with the same ghc. Isn’t it basically a dir with .hie and object files in both cases? | 20:55:26 | |
24 Jul 2025 | ||
00:12:02 | ||
Hi everyone, is there a Haskell specific Nix beginner guide out there? | 00:14:32 | |
I think it's a bit fragmented depending on your needs / approach as can be seen in this thread https://www.reddit.com/r/haskell/comments/1cqfboq/latest_guidance_on_using_haskell_with_nix/ . Some years ago my searches often ended up here https://haskell4nix.readthedocs.io/ | 00:45:35 | |
I would suggest you start wo using these evolved approaches and try to have as few layers on top of "vanilla"/"flakes" nix | 01:09:48 | |
Thank you! | 01:51:31 | |
There seems to be a thousand ways to do it which is confusing for a newbie | 01:56:06 | |
05:41:12 | ||
Hello! I'm trying to build a nixpkgs.haskellPackages from an arbitrary stackage snapshot. I just found regenerate-hackage-packages.sh in nixpkgs and also hackage2nix in cabal2nix . Is hackage2nix enough for my purpose? I don't fully understand how two tools differ. | 05:54:08 | |
@keetonbrewster:matrix.org haskell4nix.readthedocs.io is outdated. It's uptodate version is the nixpkgs manual Haskell section. | 06:07:02 | |
In reply to @bglgwyng:matrix.orgHuh, I don't think we expect downstream users of hackage2nix. I fear that you won't get very far. But if you really want do this the easiest way would probably be to look at the update stackage script in nixpkgs modify it to not use the newest but your desired snapshot, run it and then run the regenerate script. You can think of the regenerate script as running hackage2nix with all correct configuration for nixpkgs in place. Running hackage2nix without it would probably require duplicating parts of it. | 06:15:22 | |
What if I want to avoid making my own version of nixpkgs? I prefer more local apporach such as generating .nix file that can be used to replace nixpkgs.haskellPackage . Can I do the same thing using 'regenerate-hackage-packages'? | 06:45:03 | |
It's not meant to be used that way, no. But maybe you can take it as an inspiration. Maybe you want to have a look at stacklock2nix it might be closer to your needs. | 06:47:25 | |
Do you mean https://github.com/cdepillabout/stacklock2nix this repo? | 06:59:05 | |
In reply to @keetonbrewster:matrix.orgThat reminds me. I actually did a talk about that at zurihac. It might be helpful: https://m.youtube.com/watch?v=xOjKAatxD_g&list=PLOvRW_utVPVlFEXuyaIVILO1t_48e4Ai2&index=9&pp=iAQB | 06:59:34 | |
Indeed, I tried an approach using 'plan.json', cabal dry run generates plan.json and nix fetches the source code, however it caused too frequent rebuild of existing library. So I'm looking for a way to pre-bake package set. | 07:01:47 | |
In reply to @maralorn:maralorn.deIt's sadly not super structured or dense, but I actually think we covered a lot of useful information. | 07:04:59 | |
Hey guys. what is the current status of static linking with ghc? Is ghc 9.4.8 still the only supported compiler? | 08:51:07 | |
all GHCs work, but TemplateHaskell isn't supported for >= 9.6 | 10:02:35 | |
out of interest, is there a ticket that tracks this? | 10:38:26 | |
found it: https://github.com/NixOS/nixpkgs/issues/275304 | 10:38:45 | |
teo (they/he): I will try out with your patch and report back. thank you! | 12:44:14 | |
25 Jul 2025 | ||
Hmm... I think I might be doing something wrong. So I have this bare-bones starter project of mine: https://github.com/IQubic/mandelbrot | 00:10:59 | |
And entering the
| 00:12:02 | |
Does cabal not support GHC2024 yet? | 00:12:13 | |
In reply to @mequbic:matrix.org
When I explicitly install a newer version using (Well "works": I get a different error, which could be resolved with changing | 05:49:07 | |
In reply to @le:4d2.org To have all of this in your shell.nix, change
to
| 05:55:45 | |
I need some help understanding this build failure from PR 424162. | 06:12:38 | |
In reply to @aidalgol:matrix.orgIt looks like 8 test failures caused by an attempt to run a missing or not found program. Check the source code to see what it's trying to execute and try to add it to the test dependencies. Since these appear to be doctests, they might be failing because the build doesn't have the necessary tools to run doctests available. | 08:22:40 | |
teo (they/he): which hadrian needs your patch? The boot compiler or the actual compiler? (the patch only applies to ghc 9.10 but not to 9.12...) | 10:59:43 |