| 4 Feb 2025 |
 magic_rb | https://codeberg.org/magic_rb/percept-web/src/branch/master/flake.nix#L23 | 08:12:39 |
| magic_rb | Ah sorry this id where i found it | 08:12:47 |
 Axman6 | I did also come across: https://gitlab.haskell.org/haskell-wasm/ghc-wasm-meta | 08:13:04 |
| magic_rb | Ah it downloads binary releases and them nixifies them | 08:14:37 |
| magic_rb | https://gitlab.haskell.org/haskell-wasm/ghc-wasm-meta/-/blob/master/autogen.json?ref_type=heads | 08:14:42 |
 Alex | In reply to @axman6:matrix.org
so pkgsCross.wasi32.hostPackages.ghc121 or something? For compilers, you probably want buildPackages, not hostPackages. | 08:47:48 |
| Alex | Summary:
pkgsCross.aarch64-multiplatform.ghc - GHC built on current platform, runs on aarch64, targets aarch64pkgsCross.aarch64-multiplatform.buildPackages.ghc - GHC built on current platform, runs on current platform, targets aarch64 | 08:54:18 |
 alexfmpe | don't think there's much in the way of ghc wasi support though? https://github.com/NixOS/nixpkgs/pull/225000#issuecomment-1622683134 | 08:59:24 |
| alexfmpe | pkgsCross.ghcjs.haskell.packages.ghc912.hello is in good shape though | 09:00:22 |
 sterni (he/him) | Yes, we don't support the GHC wasm backend since it is basically a parallel world, requiring its own forks of LLVM and wasi-sdk which we would like to avoid maintaining | 13:35:19 |
| sterni (he/him) | especially LLVM is a problem since we have non trivial patches ourselves and IIRC the wasm ghc ones apply cleanly on top | 13:35:57 |
| sterni (he/him) | Eventually, we'll probably have to bite the bullet, though, I did not get the impression that this situation will improve any time soon | 13:36:38 |
 MangoIV | In reply to @sternenseemann:systemli.org
Eventually, we'll probably have to bite the bullet, though, I did not get the impression that this situation will improve any time soon It could live in nix-Community instead of nixpkgs perhaps? I have started doing this at some point but only got as far as building the compiler | 16:37:27 |
| MangoIV | In reply to @sternenseemann:systemli.org
Eventually, we'll probably have to bite the bullet, though, I did not get the impression that this situation will improve any time soon * It could live in nix-community instead of nixpkgs perhaps? I have started doing this at some point but only got as far as building the compiler | 19:11:59 |
|  @serodrsm:matrix.org joined the room. | 23:22:49 |
| @serodrsm:matrix.org | Hallo | 23:22:58 |
| @serodrsm:matrix.org left the room. | 23:33:28 |
 maralorn | Huh | 23:38:55 |
| maralorn | I just today learned about: https://nohello.net/en/ | 23:39:14 |
| sterni (he/him) | MangoIV: yes I was also thinking about having an overlay, I have been talking to dmjio (who started working on such an overlay) about that. I was meaning to look at the code they came up with when I have some time again | 23:40:09 |
 Collin Arnett | In reply to @maralorn:maralorn.de
I just today learned about: https://nohello.net/en/ Yeah really like that one. | 23:40:55 |
| Collin Arnett | Wish I could use it at work | 23:41:06 |
| 5 Feb 2025 |
| Axman6 | is there also a dontasktoaskjustask.net? Rule #1 of IRC | 01:25:15 |
|  bdesham joined the room. | 01:29:30 |
| bdesham | Hi all. One of the packages I maintain was listed as broken in the big “Stackage LTS 22 -> 23” PR. I’ve released a new version to Hackage that (hopefully) fixes the problem. Do I need to do anything more to incorporate that new version into this PR? | 01:30:08 |
| Collin Arnett | In reply to @axman6:matrix.org
is there also a dontasktoaskjustask.net? Rule #1 of IRC https://dontasktoask.com/ | 02:32:42 |
| 6 Feb 2025 |
| alexfmpe | In reply to @bdesham:matrix.org
Hi all. One of the packages I maintain was listed as broken in the big “Stackage LTS 22 -> 23” PR. I’ve released a new version to Hackage that (hopefully) fixes the problem. Do I need to do anything more to incorporate that new version into this PR? It should become available with the next hackage bump. If you're in a hurry you can patch it in but that's somewhere between trivial and annoying | 13:07:42 |
| alexfmpe | Might need to mypkg=mypkg_1_2_3 if stackage LTS doesn't pick it up (e.g. if it causes breakage) | 13:08:54 |
 lambdatheultimatealias | Speaking of which, I raised a PR on haskell-updates with the result of running regenerate-hackage-packages.sh for my package only. Was this necessary and right? It stops the package breaking and has the advantage that there is no cleanup after the next hackage pull. | 13:41:13 |
| maralorn | In reply to @lambdatheultimatealias:matrix.org
Speaking of which, I raised a PR on haskell-updates with the result of running regenerate-hackage-packages.sh for my package only. Was this necessary and right? It stops the package breaking and has the advantage that there is no cleanup after the next hackage pull. That's good, if it is the only thing you touched. | 13:52:30 |
