| 17 May 2025 |
 maralorn | * When you say recent error could it be that it was part of the big 9.6 -> 9.8 bump which reached master about two weeks ago? | 12:30:29 |
 ners | In reply to @maralorn:maralorn.de
When you say recent error could it be that it was part of the big 9.6 -> 9.8 bump which reached master about two weeks ago? Yeah, that looks about right. Building it on the nixos-24.11 branch where there is still GHC 9.6.6 does not have that error. | 12:37:07 |
| ners | (it's still broken because of depependency bounds) | 12:37:18 |
| maralorn | Huh, I mean it is a custom Setup.hs. | 12:43:49 |
| maralorn | At least the header indicates that. | 12:44:06 |
| maralorn | I wonder if it works if you just rm it in the postPatch phase. | 12:44:33 |
| ners | It does! Thanks for the tip. :) | 12:46:37 |
| ners | I'll open a PR against haskell-updates. | 12:47:01 |
| ners | * I'll open a PR against haskell-updates to unbreak it. | 12:47:06 |
| maralorn | I guess this has something to do with the recent modification of cabal build types, yet the error message is a bit baffling. | 12:47:38 |
| ners | Do you think it makes sense to open a PR upstream removing the Setup.hs? I never quite understood what purpose that file serves. | 12:48:13 |
 winston | my understanding is that it's basically the equivalent of a Makefile? like running
runhaskell Setup configure
runhaskell Setup build
runhaskell Setup install
| 12:51:29 |
| winston | i actually ran into issues not having a Setup.hs present when I tried to package some of my code for other Distros like Arch | 12:51:48 |
| maralorn | I feel semi comfortable giving advice on this without understanding the problem. 😄 But yeah my general heuristic is that packages which don’t need special setup shouldn’t ship their own Setup.hs. The nixpkgs builder uses a fallback when that happens. | 12:54:25 |
