| 5 Jun 2021 |
 sterni (he/him) | the way I'd do it is to pass an argument defaultCompilerBroken to hackage-packages.nix | 11:32:03 |
| sterni (he/him) | and always emit broken = defaultCompilerBroken; | 11:32:12 |
 maralorn | hm, that will be a lot more characters. And I don‘t understand it exactly. That variable would be a bool we set to true when we are evaluating for the default compiler? | 12:33:06 |
| maralorn | If so I imagine a broken = forDefaultCompiler would work better? | 12:33:34 |
| maralorn | Regarding to stackage-nightly. I am curious how much worse it would be to just not update stackage at all for a few weeks (or maybe even months?) compared to staying on LTS. | 12:37:01 |
| maralorn | otoh, when switching to LTS would mean nearly no package downgrades we could just switch. | 12:38:14 |
| maralorn | Or do you think the community will grow unsatisfied if we hop in between?^^ | 12:39:03 |
 joe (he/him) | nixpkgs is going back to lts? | 12:39:11 |
| joe (he/him) | sorry, perhaps I should read the conversation | 12:39:19 |
 Las | What is the problem with GHC 9 support anyway? | 12:39:29 |
| maralorn | Las: Mainly that haskell-language-server is not ghc 9 compatible, yet. | 12:39:56 |
| Las | Couldn't just haskell language server stay on GHC 8.10? | 12:40:15 |
| maralorn | Las: No, no way. Completely impossible. | 12:40:33 |
| sterni (he/him) | In reply to @maralorn:maralorn.de
If so I imagine a broken = forDefaultCompiler would work better? yeah well naming is the other thing always :) but that would be the idea indeed | 12:40:39 |
| maralorn | In reply to @Las:matrix.org
Couldn't just haskell language server stay on GHC 8.10? I mean we could still deliver an 8.10 hls to the users. But they wouldn‘t be able to use it on their haskellPackages packages. | 12:41:39 |
| Las | makes sense | 12:41:48 |
| maralorn | Maybe that’s something we need to swallow. But it would completely break my use case for nixpkgs and I would likely quickly loose interest in maintaining it.^^ | 12:42:40 |
| Las | Is there some overview of why it's broken on GHC 9? I couldn't find anything on their GitHub | 12:42:49 |
| joe (he/him) | isn't it one of the pinned issues? | 12:43:24 |
| Las | you are right | 12:43:39 |
| maralorn | Las: They have an issue about it. The problem is that GHC changed a lot of their internal APIs including nearly all of their Module names and hls links directly against their internal API. | 12:44:11 |
| Las | That sounds unfortunate | 12:44:30 |
| Las | https://github.com/haskell/haskell-language-server/pull/1635 It seems to have basic support since a few days ago? | 12:45:40 |
| Las | There is also https://github.com/haskell/haskell-language-server/pull/1649 | 12:46:21 |
 toonn | Las: Maybe haskell.nix is a better fit for you. | 12:51:39 |
| Las | Maybe yeah | 12:52:06 |
| toonn | The Nixpkgs Haskell infra's primary (only?) goal is to facilitate providing Haskell programs in Nixpkgs. | 12:52:18 |
| maralorn | toonn: That’s not how I see it. | 12:52:33 |
| toonn | It's really cool how usable it can be for general development but that is not it's goal. | 12:52:50 |
| toonn | *its | 12:53:11 |
