| 22 Apr 2025 |
 alexfmpe | that to me already looks like "hey haskell foundation, platform us because everything else is even worse" | 12:09:29 |
| alexfmpe | "and not just on april 1st like ghcup did" | 12:09:43 |
| alexfmpe | now imagine getting mobile cross back in shape | 12:10:03 |
| alexfmpe | plus this | 12:10:29 |
| alexfmpe | at that point, if I was maintaining some nix jungle I'd just hook onto this train instead to get the scale economy | 12:11:09 |
| alexfmpe | so maybe the way to sell it to the rest of overlayland is just making their payoff bigger | 12:12:47 |
| alexfmpe | and then hopefully they build their own cart connector | 12:13:01 |
| alexfmpe | that's somewhat what happened with miso and reflex-dom in recent months | 12:13:31 |
| alexfmpe | they both build with 9.12 js backend outta haskell-updates | 12:14:06 |
| alexfmpe | so now it's just about keeping it building | 12:14:32 |
| alexfmpe | (reflex-platform still has a bunch of stuff for mobile) | 12:15:25 |
 emily | if Stackage LTS QA is actually as minimal as claimed here then it seems like tracking nightly would be an easy way to avoid painful flag days / long-lived branches with less risk than I expected | 12:16:47 |
 Teo (he/him) | I think more sharing between nixpkgs and head.hackage would be great. head.hackage used to use the nixpkgs infra to build stuff so it's not inconceivable that it could do that again. At some point I want to write a little cli for head.hackage to help track upstream PRs etc, since it's a huge pain atm, and often PRs are just not made to the upstream. Nixpkgs is much better in this regard | 12:18:06 |
| alexfmpe | apparently I'm wrong, stackage site claims they do run test suites | 12:18:21 |
| alexfmpe | they just don't patch things, | 12:18:40 |
| alexfmpe | * they just don't patch things | 12:18:44 |
| 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 |
| alexfmpe | * It's insane to me they don't run test suites
EDIT: me wrong. Stackage does run (native) test suites, they just don't patch stuff | 12:37:51 |
| Teo (he/him) | Redacted or Malformed Event | 12:44:39 |
