Haskell in Nixpkgs/NixOS | 717 Members | |
| For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/ | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org | 142 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Aug 2025 | ||
| 18:40:18 | |
| 19 Aug 2025 | ||
In reply to @artem.types:matrix.orgI've previously gotten it to work without doing anything special. I have no idea what's wrong with your case. | 00:51:40 | |
| Does haskell.nix internally generate plan.json and use it? Or it just uses pre-built package sets. | 06:18:16 | |
| bglgwyng: haskell.nix uses plan.json (at least that’s one of the available modes) | 06:53:04 | |
FTW: I made this typo again: liquidhaskell-boot = doJailbreak super.smtlib-backends-tests; and that's why liquidhaskell couldn't find a module in liquidhaskell-boot... | 14:09:50 | |
* FTR: I made this typo again: liquidhaskell-boot = doJailbreak super.smtlib-backends-tests; and that's why liquidhaskell couldn't find a module in liquidhaskell-boot... | 14:17:52 | |
| 14:23:55 | ||
| what is the better commit message / PR title for a nixpkgs PR:
or
| 14:28:57 | |
| * what is the better commit message / PR title for a nixpkgs PR:
or
? | 14:29:02 | |
| the ci parses commit messages, so if you do one commit per package it will build the right packages | 14:34:20 | |
| ouch, I did one commit for everything! just to double-check: is one commit per package a requirement? | 14:40:19 | |
| no | 14:42:05 | |
it will parse {a,b} in commit messages too | 14:56:04 | |
| all right, I'll go with the explicit list then | 14:59:09 | |
| oh cool | 15:16:34 | |
| waaaat | 16:30:59 | |
| where can I find these tidbits | 16:31:14 | |
| it's in the ofborg repo docs I think | 16:31:57 | |
| TIL | 16:42:39 | |
| https://github.com/NixOS/ofborg?tab=readme-ov-file#automatic-building | 16:42:40 | |
| 20 Aug 2025 | ||
I've looked at documentation and source code but I don't see how I can use developPackage and add additional packages to the environment (ideally they would only be added when using a shell). I guess that's done with the modifier attribute? | 18:02:08 | |
| (I'd like to add packages like HLS and hlint) | 18:02:32 | |
| how do I get a sense of when the GHC 9.10 bump will be merged into staging? I saw a long list of failures but surely not everything has to be fixed before the merge. I also saw "We only do the merge if the mergeable job is succeeding on hydra" but how do I get a sense of close it is to succeeding? | 19:39:21 | |
| Artem: I am not sure anyone has it. We probably want to fix most of the errors here before merging: https://github.com/cdepillabout/nix-haskell-updates-status | 20:04:11 | |
| Last ghc bump took 4 to 5 months. But that was the worst one I can remember. We normally aim at one month and two are realistic. | 20:04:13 | |
| 23 Aug 2025 | ||
In reply to @kephaspierre:matrix.orgThis is how I do it. At least at the moment, things change as I learn more Nix. https://gitlab.com/magus/nix-setups/-/tree/main/hs-shell?ref_type=heads | 15:34:30 | |
| Eval with Stackage LTS 24.6 https://hydra.nixos.org/eval/1817909?compare=1817896 | 22:01:32 | |
In reply to @magthe:tchncs.deI finally found a way where I wrote the least possible amount in my shell.nix, I do import project.nix (I run cabal2nix . > project.nix when my cabal file changes), and I use builtins.functionArgs to see every package I need, and use that in a pkgs.mkShell { packages = [ pkgs.hlint pkgs.haskell-language-server (pkgs.haskellPackages.ghcWithPackages getDeps)] | 23:26:40 | |
| 24 Aug 2025 | ||
if you have the generated file you can just use haskell.packages.${your-pkg-set}.shellFor { packages = p: [ (p.callPackage ./project.nix { }) ]; nativeBuildInputs = [ /* other tools */ ]; }. | 14:10:00 | |
| I no longer use nix for haskell packages, they're always out of date with hackage, so I just have my shell.nix including the correct ghc and cabal and then use cabal for the rest | 14:34:34 | |