!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

695 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 infrastructure138 Servers

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


SenderMessageTime
15 Sep 2025
@mangoiv.:matrix.orgMangoIVbut it would for sure require support of cabal upstream, right? I don't think that that's a good idea at all tbh. 13:41:25
@teoc:matrix.orgteo (they/he) This didn't actually achieve it but we had this MR ages ago: https://gitlab.haskell.org/ghc/ghc/-/merge_requests/5965 13:42:24
@emilazy:matrix.orgemily I would personally only expose a fully bootstrapped one as first-class but it's not my decision to make. probably having a withHugsBootstrap param on the MicroHs derivation and microhs takes microhs as a build input that you override to have withHugsBootstrap or something 13:42:33
@mangoiv.:matrix.orgMangoIVAlso why does hadrian not support proper incremental build support? 13:42:37
@emilazy:matrix.orgemilyI mean whatever makes the Nix simplest really13:42:41
@mangoiv.:matrix.orgMangoIVshake does that out of the box? 13:42:43
@emilazy:matrix.orgemilybut even for bootstrapping GHC I think you'd want the full MicroHs13:42:54
@sternenseemann:systemli.orgsterniI guess nothing inherently, it's just that it's an incomplete reimplementation of the old make build system with some arbitrary improvements. It regressed a bunch of stuff that hasn't been fixed to this day. I find it much more unwieldy to work with and understand because it uses kind of fuzzy abstractions and it is hard to inspect what it decides to do internally and even harder to override certain aspects of its behavior. Also there are questionable design decisions like always building an bindist instead of installing directly (this sounds good in theory, but is not really a good idea).13:43:00

Show newer messages


Back to Room ListRoom Version: 6