| 15 Sep 2025 |
 Alex | In reply to @emilazy:matrix.org
we talked about this recently and I suggested a package set would be interesting for exploring future GHC bootstrap How should I structure this btw?
Should Nixpkgs expose:
- Any Hugs-interpreted boot tools (probably not, likely fragile)?
- Stage 1 compiler built via Hugs (should be as good as a stage 2)?
| 13:40:43 |
 emily | I didn't realize it was that close to "just" being cabal-installable | 13:40:46 |
| emily | I assumed you'd need a lot more glue. cool | 13:40:52 |
 MangoIV | but 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 |
 Teo (he/him) | 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 |
| emily | 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 | Also why does hadrian not support proper incremental build support? | 13:42:37 |
| emily | I mean whatever makes the Nix simplest really | 13:42:41 |
