!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

685 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://nixos.org/manual/nixpkgs/unstable/#haskell | Current PR: https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates | Maintainer Docs: https://github.com/NixOS/nixpkgs/blob/haskell-updates/pkgs/development/haskell-modules/HACKING.md | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org | Merger Schedule: https://cloud.maralorn.de/apps/calendar/p/H6migHmKX7xHoTFa/dayGridMonth/now | Join #haskell.nix:libera.chat for question about the alternative haskell.nix infrastructure136 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
5 Sep 2025
@maralorn:maralorn.demaralornAaah, what is the point of having ghc-lib-parser spanning three ghc versions when fourmolu and ormolu track cabal-syntax anyway which is tightly coupled to the ghc release …12:16:17
@maralorn:maralorn.demaralornI have now the choice of downgrading ghc-lib-parser, fourmolu and ormolu to build hls on ghc 9.10 or to upgrade Cabal/Cabal-syntax. Both either globally or in a quite large overrideScope.12:17:35
@maralorn:maralorn.demaralornI feel like I am overlooking something because that didn’t feel as painful before …12:18:04
@artem.types:matrix.orgArtem maralorn: the very strict bounds that Ormolu puts on Cabal-syntax look strange. I'd ask on their bug tracker exactly the question you're posing above: if you use ghc-lib-parser, you probably want to span over at least couple of GHC, but you also always limit Cabal-syntax to one version, so this looks like mixed messages... They always bump Cabal-syntax when they bump ghc-lib-parser, so they at least understand some connection they just overly pessimistic about it it looks like. 15:10:21
@maralorn:maralorn.demaralornI guess using ghc-lib-parser might have other advantages than just the compatibility range …15:14:22
@artem.types:matrix.orgArtemmaybe, but there seems to be no reason to be as strict about Cabal-syntax bounds: they use just a few basic things from it, and those don't really change15:20:45
@maralorn:maralorn.demaralornOkay15:22:12
@maralorn:maralorn.demaralornIt seems I am loosing my grip on being the nixpkgs maintainer when I didn’t first check whether a jailbreak works. 😄15:22:36
@maralorn:maralorn.demaralorn* It seems I am loosing my grip on being a nixpkgs maintainer when I didn’t first check whether a jailbreak works. 😄15:22:44
@maralorn:maralorn.demaralornFTR, it didn’t.23:05:12
6 Sep 2025
@sternenseemann:systemli.orgsternithe answer seems to be: detective work10:42:24
@sternenseemann:systemli.orgsterniit is also extremely annoying to tell what versions of GHC a commit has been backported to10:42:49
@teoc:matrix.orgteo (they/he)Once you find the MR then you should be able to know the backporta since release managers leave comments when stuff gets backported, but all of it is so much friction. I occasionally consider writing a little web service to get this type of info11:01:37
@sternenseemann:systemli.orgsterniI guess best bet is to go via the linked issue if there's one in the commit message since that's a requirement now11:04:31
@sternenseemann:systemli.orgsterni maralorn: Cabal-syntax is reinstallable, ghc not; so that's probably the reason 11:05:00
@maralorn:maralorn.demaralorn
In reply to @sternenseemann:systemli.org
maralorn: Cabal-syntax is reinstallable, ghc not; so that's probably the reason
Good point
11:11:59

Show newer messages


Back to Room ListRoom Version: 6