| 26 Oct 2025 |
 alexfmpe | * should shellFor have a
withCabal boolean or so?
in the native case it can just go in nativeBuildInputs, but since for cross shellFor what we place in PATH isn't `ghc` but `<prefix>-ghc` you need this sort of wrapping https://gitlab.haskell.org/haskell-wasm/ghc-wasm-meta/-/blob/104d440e93fc05fefd36441e95013eda4b06f611/pkgs/wasm32-wasi-cabal.nix#L62-67
another option is having unprefixed `ghc`, `ghc-pkg`, etc point to the prefixed ones | 15:37:42 |
| alexfmpe | * should shellFor have a `withCabal` boolean or so?
in the native case it can just go in nativeBuildInputs, but since for cross shellFor what we place in PATH isn't `ghc` but `<prefix>-ghc` you need this sort of wrapping https://gitlab.haskell.org/haskell-wasm/ghc-wasm-meta/-/blob/104d440e93fc05fefd36441e95013eda4b06f611/pkgs/wasm32-wasi-cabal.nix#L62-67
another option is having unprefixed `ghc`, `ghc-pkg`, etc point to the prefixed ones | 15:40:31 |
| 27 Oct 2025 |
 sterni | well it implicitly assumes you need to compile Setup.hs | 13:47:17 |
| alexfmpe | hmm I see, you always potentially need native ghc for that | 14:24:12 |
| alexfmpe | but it makes sense to always wrap cross cabal no? otherwise what is its point | 14:32:08 |
| alexfmpe | * but it makes sense to always wrap cabal from the pkgsCros set no? otherwise what is its point | 14:32:19 |
|  amadaluzia[tde] joined the room. | 23:56:39 |
| 29 Oct 2025 |
|  NickSeagull joined the room. | 19:32:52 |
| 30 Oct 2025 |
| sterni | difficult question imo | 06:31:28 |
| sterni | it would be nice to have the option, but it’s not clear to me how it should work | 06:31:48 |
| alexfmpe | reminds me of https://github.com/NixOS/nixpkgs/issues/237741 | 12:10:46 |
