| 30 Aug 2025 |
 sterni (he/him) | they say not doing that is “slightly risky” | 02:12:52 |
| sterni (he/him) | but you are technically conforming when everything's fine when uploading | 02:13:03 |
 maralorn | Weird. All my years reading CLC discussions had made me think that | 09:10:31 |
 toonn | Are you though? Because the PVP as written is for versioning a package, not for how to bound dependencies, no? | 09:24:25 |
 Teo (he/him) | Out of interest, how many packages did this break in nixpkgs? I would've expected everything to be updated by now. I guess it's things not on Stackage? | 10:15:42 |
|  Uraraka ~ Ochaco changed their profile picture. | 15:30:24 |
| Uraraka ~ Ochaco changed their display name from data Void to Peri. | 15:31:02 |
|  @Las:matrix.org left the room. | 22:01:28 |
| 31 Aug 2025 |
 lxsameer | hey folks, do nixpkgs contain the webassembly backend of GHC? | 17:38:15 |
| Uraraka ~ Ochaco | most of it, it just requires a little patching by this gitlab.haskell.org/haskell-wasm/ghc-wasm-meta | 17:39:00 |
| lxsameer | what's the package name? | 17:39:18 |
| maralorn | In reply to @lxsameer:matrix.org
hey folks, do nixpkgs contain the webassembly backend of GHC? Not really. no. | 17:39:57 |
| Uraraka ~ Ochaco | normally I just do (builtins.getFlake "gitlab:haskell-wasm/ghc-wasm-meta?host=gitlab.haskell.org").packages.x86_64-linux.all_9_12 in a shell.nix | 17:40:32 |
| Uraraka ~ Ochaco | a little patching later then I have wasm32-wasi-cabal, wasm32-wasi-ghc etc | 17:41:13 |
| lxsameer | ahhh, so that repo exports whatever is necessary for the wasm stuff. cool | 17:42:39 |
| Uraraka ~ Ochaco | pretty much good enough for most stuff | 17:42:57 |
| maralorn | There is this https://github.com/ners/nix-wasm | 17:43:10 |
| maralorn | And what peri posted should be enough to play around | 17:43:47 |
| Uraraka ~ Ochaco | I couldn't figure out the benefit to that over ghc-wasm-meta | 17:44:12 |
| Uraraka ~ Ochaco | it imports ghc-wasm-meta and does some flakey things | 17:44:30 |
| Uraraka ~ Ochaco | maybe it's to make things nix-buildable?
either way a full install with prefix will still build manually | 17:45:04 |
| lxsameer | Peri, i never tried any wasm related stuff on haskell. is it ok to use any prelude? | 17:45:13 |
| Uraraka ~ Ochaco | I presume so, everything non-network-related seemed to work for me | 17:45:35 |
| Uraraka ~ Ochaco | I wrote a reflex-dom app with it | 17:46:07 |
| Uraraka ~ Ochaco | wth a load of servant in it | 17:46:22 |
| lxsameer | cool cool. seems like i can handle my workload with it | 17:46:47 |
| maralorn | In reply to @dandart:matrix.org
maybe it's to make things nix-buildable?
either way a full install with prefix will still build manually Yes, it is to make things nix buildable. | 17:46:50 |
| maralorn | But it's still very rough around the reges. | 17:48:16 |
| maralorn | * | 17:48:26 |
| Uraraka ~ Ochaco | I kind of gave up nix-building haskell projects because I wanted to keep up with hackage versions (and especially text 2.1.2) - I had to keep jailbreaking things but the package versions in nixpkgs unstable / haskell-updates were still very behind. I presume they were up to date with various stackage snapshots but I don't use stack as I end up missing updates.
I ended up just doing it by getting only ghc and cabal through nix-shell, and then getting cabal to do everything cabal style. That way I can allow people who don't want to use nix be able to do things just as well with ghcup.
hence haven't tried to nix-build any haskell bits in a good while. | 17:52:03 |
