| 18 Sep 2025 |
 iqubic (she/her) | Nevermind... I'm a moron. Looking at the code in Nixpkgs, with_alsa is a default flag for this package. | 19:20:34 |
| 19 Sep 2025 |
 bglgwyng | I found that plan.josn doesn't contain .cabal's default-extensions information. Doesn't it indicate that it's not possible to reproduce cabal build only with plan.json + ghc? | 08:22:36 |
 sterni (he/him) | iqubic (she/her): otherwise haskell.lib.compose.enableCabalFlag would be the answer. | 10:21:39 |
| sterni (he/him) | bglgwyng: yes and there are also other tasks that Cabal needs to do which is required for some packages to work | 10:23:00 |
| sterni (he/him) | e.g. autogen-modules. I don't know if there are even more basic things Cabal needs to do, not really familiar with the details | 10:23:45 |
| bglgwyng | it seems generic-builder runs Setup.hs to build cabal packages. | 11:00:03 |
| bglgwyng | Do we have modificatino related to ghcWithPacakges between nixpkgs/nixos-25.05 and nixpkgs/HEAD? With nixos-25.05, I found ghcWithPackages builds two random packages with the same version, but with HEAD, it doesnt'. | 11:09:43 |
| bglgwyng | * Do we have modificatino related to ghcWithPacakges between nixpkgs/nixos-25.05 and nixpkgs/HEAD? With nixos-25.05, I found ghcWithPackages builds two random packages with the same version, but with HEAD, it builds only one. | 11:11:42 |
 maralorn | I mean it’s generally much more likely that this is to due to differences in a specific package. But I remember vaguely that we merged something related to ghcWithPackages in the last months. | 11:12:26 |
| bglgwyng | Could you share the commit ref please? I want to compare before and after. | 11:13:43 |
| maralorn | Huh, er maybe we didn’t merge it and it was just a PR. | 11:13:50 |
| bglgwyng | Hm... then now I am going to start binary search over then lol | 11:14:20 |
| maralorn | Huh, I can’t find anything that makes sense. | 11:16:13 |
| maralorn | Could be d3e4f784aa1bb95ad8a13cadc7073e6617658f2f, but seems highly unlikely. | 11:16:32 |
