!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

721 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.org143 Servers

Load older messages


SenderMessageTime
5 Jun 2021
@sternenseemann:systemli.orgsterni (he/him)I think we should make the broken list limited to the default GHC somehow10:23:55
@sternenseemann:systemli.orgsterni (he/him)it may be very annoying to deal with marked-as broken packages on GHC 9 which have just been marked as broken because they require the newer base or time library10:24:29
@sternenseemann:systemli.orgsterni (he/him)although it is probably an extra eval time cost to manage this separately10:24:46
@maralorn:maralorn.demaralornI am not sure about this.10:25:51
@maralorn:maralorn.demaralornThe broken state between different ghc versions is probably highly correlated if you compare it across the whole package set.10:27:13
@ahdyt:matrix.orgahdytis that broken state also cause hls to crash?10:45:11
@maralorn:maralorn.demaralorn ahdyt: I don‘t understand. 10:45:39
@sternenseemann:systemli.orgsterni (he/him) maralorn: but it doesn't matter since we don't build the other sets anyways 11:05:16
@sternenseemann:systemli.orgsterni (he/him)it is let fan service11:05:19
@sternenseemann:systemli.orgsterni (he/him) * it is les fan service11:05:25
@sternenseemann:systemli.orgsterni (he/him) * it is less fan service11:05:29
@sternenseemann:systemli.orgsterni (he/him)but the non default package sets are always gonna be broken in suprising ways…11:05:44
@maralorn:maralorn.demaralornTrue11:05:54
@maralorn:maralorn.demaralornYeah, it probably wouldn‘t be bad in principle. But I am not sure how to do it.11:06:43
@maralorn:maralorn.demaralornI think using the broken flags in hackage-packages.nix seems reasonable.11:07:05
@maralorn:maralorn.demaralornMaybe we insert a step, when evaluating a non standard ghc that strips all broken flags right after loading hackage-packages but before applying any other overrides?11:08:11
@maralorn:maralorn.demaralornThat way we pay no additional cost on the standard ghc.11:08:24
@maralorn:maralorn.demaralornAnd can keep the config as is.11:08:51
@sternenseemann:systemli.orgsterni (he/him)the way I'd do it is to pass an argument defaultCompilerBroken to hackage-packages.nix11:32:03
@sternenseemann:systemli.orgsterni (he/him)and always emit broken = defaultCompilerBroken;11:32:12
@maralorn:maralorn.demaralornhm, 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:maralorn.demaralorn If so I imagine a broken = forDefaultCompiler would work better? 12:33:34
@maralorn:maralorn.demaralornRegarding 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:maralorn.demaralornotoh, when switching to LTS would mean nearly no package downgrades we could just switch.12:38:14
@maralorn:maralorn.demaralornOr do you think the community will grow unsatisfied if we hop in between?^^12:39:03
@joe:monoid.aljoe (he/him)nixpkgs is going back to lts?12:39:11
@joe:monoid.aljoe (he/him)sorry, perhaps I should read the conversation12:39:19
@Las:matrix.orgLasWhat is the problem with GHC 9 support anyway?12:39:29
@maralorn:maralorn.demaralorn Las: Mainly that haskell-language-server is not ghc 9 compatible, yet. 12:39:56
@Las:matrix.orgLasCouldn't just haskell language server stay on GHC 8.10?12:40:15

There are no newer messages yet.


Back to Room ListRoom Version: 6