!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

Load older messages


SenderMessageTime
22 Apr 2025
@emilazy:matrix.orgemilyis the flag day b/c jumping from current LTS to current nightly will effectively be the work of an LTS bump?13:01:09
@alexfmpe:matrix.orgalexfmpeI assume that becomes closer to the truth the closer nightly is to become new LTS?13:06:06
@alexfmpe:matrix.orgalexfmpeOr is nightly just very much broken in the early days?13:08:44
@maralorn:maralorn.demaralornIts comparable yes.13:13:41
@maralorn:maralorn.demaralornIt’s often quite a lot smaller than LTS in the beginning.13:14:07
@emilazy:matrix.orgemilyand I assume the current Nightly is closer to the next LTS than the one we just bumped to? 😆13:14:33
@maralorn:maralorn.demaralorncorrect13:15:57
@maralorn:maralorn.demaralornBumping the stackage snapshot generally means bumping the ghc major version that has friction no matter how early or late we do it.13:16:41
@alexfmpe:matrix.orgalexfmpe
In reply to @maralorn:maralorn.de
It’s often quite a lot smaller than LTS in the beginning.
Huh smaller building set or smaller breakage when bumping to it?
13:19:55
@emilazy:matrix.orgemilyI assumed the former13:23:27
@alexfmpe:matrix.orgalexfmpeHuh yeah the other doesn't make much sense disregarf13:26:13
@alexfmpe:matrix.orgalexfmpe* Huh yeah the other doesn't make much sense disregard13:26:21
@emilazy:matrix.orgemilyright, I actually first assumed the latter and then realized it must be the former :)13:27:21
@emilazy:matrix.orgemilyanyway I guess returning to the actual original point that was raised, I do feel like things are always going to be inherently difficult on some level unless the practices of the Haskell ecosystem itself change. not sure maintainers of packages supporting older and older GHCs is the answer – back in the day I remember it rather painful and it feeling like a relief to be able to rip out an old version, though maybe there's less CPP these days. ideally GHC would make fewer gratuitous breaking changes or at least do them more gracefully… (though again I understand that it's not as bad as it used to be)13:29:14
@maralorn:maralorn.demaralorn We don’t need a lot of back-compat. Maintainers should imo support [Stackage LTS … Stackage Nightly … Hackage Head] 13:31:15
@albertlarsan68:albertlarsan.frAlbert Larsan joined the room.13:45:27
@malteneuss:matrix.org@malteneuss:matrix.orgIf you have the time, could you post this idea to https://discourse.haskell.org/t/how-much-effort-does-backwards-compatibility-require-from-library-authors/11584/79 to further the discussion on this possible direction? (will get more credibility/attention coming from you)13:49:57
@maralorn:maralorn.demaralornLeft a short comment.14:09:27
@maralorn:maralorn.demaralornThis is of course in tension with ghcup keeping 9.6 the recommended ghc.14:10:14
@alexfmpe:matrix.orgalexfmpedon't see a new haskell-updates PR, guess we're focusing on fixing staging for now? rebased staging into it for now, don't think it counts as breaking, but if we want this for 25.05, best not dump a mass rebuild late in the cycle?14:31:05
@alexfmpe:matrix.orgalexfmpeessentially this means you can use the js backend in nixpkgs for browser, not only node I mean, technically you already can, but need to mess with intermediates14:32:33
@sternenseemann:systemli.orgsternihttps://www.stackage.org/diff/lts-23.19/nightly-2025-04-22 looks like it would be a big pain upgrading at the moment with even more patching14:32:48
@alexfmpe:matrix.orgalexfmpey'know, I wonder if our ghc-default+0.2 package set ends up out-building nightly14:34:52
@alexfmpe:matrix.orgalexfmpejust due to our sheer mass of overrides14:35:05
@alexfmpe:matrix.orgalexfmpeheck, we have reflex-dom and miso building with +0.4, and the former is pretty heavy dependency wise14:36:07
@alexfmpe:matrix.orgalexfmpeyeah a lot of packages will have older versions, but so many more actually build14:38:01
@sternenseemann:systemli.orgsterniIMO you can't track nightly really because the quality varies a lot (which makes sense since it is used to prepare LTS which is of relatively consistent quality). Whenever Nightly switches to the next GHC version basically nothing will work. What you can do is anticipate an LTS release by jumping to Nightly, but in principle this should be more painful than just waiting for LTS.14:39:04
@alexfmpe:matrix.orgalexfmpemakes sense still, I wonder if there's no way to work closer and have smaller jumps without straight up becoming the source of truth for stackage14:40:40
@sternenseemann:systemli.orgsterniIt is important to highlight that when we were tracking Nightly it was a special moment in the ecosystem where a bunch of huge breaking changes happened coinciding with GHC 8.10 -> 9.0/9.2. Back then there was a long time until Nightly was forked into LTS since they were waiting on some stuff that took a long time to get fixed.14:40:41
@sternenseemann:systemli.orgsterniPresumably we got around this by patching a lot of stuff since this was also 2021 ish when we did invest a lot of free time, were more people and generally more motivated.14:41:23

Show newer messages


Back to Room ListRoom Version: 6