!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

724 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.org145 Servers

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


SenderMessageTime
16 Mar 2025
@maralorn:maralorn.demaralorn Tristan Ross: I don’t think that has anything to do with the LLVM bump stuff, which seems relatively independent anyway. I can’t judge that PR, but the problem with it is figuring out whether it works. If it does work we can basically merge it at any time, independently of the following:
I want to highlight a different possibility: sterni and I settled on the deprecation policy, which I will announce (with a request for feedback) shortly. With that settled we are free to remove multiple old ghc versions once all in-tree consumers have been resolved. I guess the only point of contention is that we didn’t announce those deprecations in the last release notes after all, so if we want to stay true to that policy we probably should aim to drop them directly after 25.05 and announce the deprecation in 25.05. I know this is slower than you wanted this. But at least it is a solution. Would that be okay?
09:31:45
@maralorn:maralorn.demaralorn cc emily 09:31:59
@maralorn:maralorn.demaralorn(I know I promised stuff before, but this time I will keep it.)09:36:28
@emilazy:matrix.orgemilycool to hear, is it the "same versions as HLS" policy or some other one? have the bootstrapping concerns been worked out?14:12:53
@rosscomputerguy:matrix.orgTristan Ross
In reply to @maralorn:maralorn.de
Tristan Ross: I don’t think that has anything to do with the LLVM bump stuff, which seems relatively independent anyway. I can’t judge that PR, but the problem with it is figuring out whether it works. If it does work we can basically merge it at any time, independently of the following:
I want to highlight a different possibility: sterni and I settled on the deprecation policy, which I will announce (with a request for feedback) shortly. With that settled we are free to remove multiple old ghc versions once all in-tree consumers have been resolved. I guess the only point of contention is that we didn’t announce those deprecations in the last release notes after all, so if we want to stay true to that policy we probably should aim to drop them directly after 25.05 and announce the deprecation in 25.05. I know this is slower than you wanted this. But at least it is a solution. Would that be okay?

the problem with it is figuring out whether it works. If it does work we can basically merge it at any time

If I spin up a build of it on my ARM hardware and it passes, is that good for it to merge? The PR simply moves LLVM 12 to 13 and 15.

I want to highlight a different possibility: sterni and I settled on the deprecation policy, which I will announce (with a request for feedback) shortly.

That'd be great

we probably should aim to drop them directly after 25.05 and announce the deprecation in 25.05. I know this is slower than you wanted this. But at least it is a solution. Would that be okay?

If we can at least try and get my PR in, I think it'll be a good compromise. 24.11 has fully working GHC, 25.05 would have the few on 12, 25.11 would drop the old ones from the sound of it.

14:55:00
@maralorn:maralorn.demaralornI can’t say anything about the bootstrapping. The purpose of the policy is to signal to everyone that resolving the bootstrapping concerns is worth it because it can be removed after that.19:37:10
@maralorn:maralorn.demaralornYeah, the policy is roughly same versions as HLS.19:38:47
@emilazy:matrix.orgemilygotcha19:43:21
@emilazy:matrix.orgemilyI haven't had too much time for Nixpkgs stuff recently but I will see if I can allocate some if stuff like that becomes the remaining blocker19:43:48
20 Mar 2025
@Las:matrix.orgLas joined the room.16:42:42
@Las:matrix.orgLas I heard alexfmpehas experience cross compiling to windows without haskell.nix? 16:43:25
@alexfmpe:matrix.orgalexfmpeeh well, I gave it a go and fixed some low hanging fruit, that's about it18:12:44
@alexfmpe:matrix.orgalexfmpehttps://github.com/NixOS/nixpkgs/pull/35774418:12:48
21 Mar 2025
@dmjio:matrix.org@dmjio:matrix.org Was AWS support totally removed from nixops ? 01:21:25
@dmjio:matrix.org@dmjio:matrix.org
       … while evaluating the attribute 'nixops_unstablePlugins.nixops-aws'
         at /nix/store/zkpypzhg52sqw7jc70l7hgfys002rbgc-source/pkgs/applications/networking/cluster/nixops/default.nix:38:9:
           37|
           38|         nixops-aws = throw "nixops-aws was broken and was removed from nixpkgs";
01:21:45
@dmjio:matrix.org@dmjio:matrix.orgis there an alternative01:21:49
@dmjio:matrix.org@dmjio:matrix.org* is there an alternative, or a patch01:21:56
@dmjio:matrix.org@dmjio:matrix.orgI rely on this pkg01:22:54

Show newer messages


Back to Room ListRoom Version: 6