| 22 Apr 2025 |
alexfmpe |
head.hackage used to use the nixpkgs infra to build stuff oh? why did they stop?
| 12:19:41 |
alexfmpe | *
head.hackage used to use the nixpkgs infra to build stuff
oh? why did they stop?
| 12:19:46 |
Teo (he/him) | See this commit message: https://gitlab.haskell.org/ghc/head.hackage/-/commit/1b616c6c48dc11dfe1e357d4250ad6882cd3224a | 12:21:21 |
alexfmpe | switching to nightly needs one eager flag day but personally I'm up for that pain if we belive it makes the long term better | 12:21:33 |
alexfmpe | * switching to nightly needs one eager flag day but personally I'm up for that pain if we believe it makes the long term better | 12:21:43 |
emily | it just seems like there's a cadence issue (from previous talk in the room) and IMO any situation where you're ending up with months-long branches off Nixpkgs is pain | 12:23:05 |
alexfmpe |
Nix's Haskell infrastructure doesn't handle flags, which can complicate building some packages
it doesn't ?
| 12:23:12 |
emily | "if it hurts, do it more often" etc. | 12:23:24 |
Teo (he/him) | Perhaps the issue here was that you wanted the solver to pick some flags and nixpkgs doesn't have a solver? Not sure exactly what he's alluding to tho | 12:24:27 |
| mightybyte joined the room. | 12:27:35 |
| @ihar.hrachyshka:matrix.org joined the room. | 12:33:31 |
alexfmpe | * But it's not an orthogonal layer we can just be agnostic to. If they have some package deep in the dependency chains that is broke but only the tests expose it, stackage will happily base other package versions around it and then we need to undo a part of that
EDIT: me wrong. Stackage does run (native) test suites, they just don't patch stuff | 12:37:03 |