2025/10/18

Newest at the top

2025-10-18 17:47:04 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) (Read error: Connection reset by peer)
2025-10-18 17:46:35 +0200ephilalethes(~noumenon@113.51-175-156.customer.lyse.net) noumenon
2025-10-18 17:46:34 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-10-18 17:43:55 +0200 <EvanR> but also analogy continues, you can lightsaber your own foot easily
2025-10-18 17:43:07 +0200 <EvanR> every Jedi builds their own light saber. You don't see Jedi download lightsaber of the week and then asking for help on how it works!
2025-10-18 17:41:55 +0200 <monochrom> And so I made a utility to adjust PATH (and pretty-print it etc) :)
2025-10-18 17:41:53 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 17:40:47 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) Inline
2025-10-18 17:35:19 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)
2025-10-18 17:30:39 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 17:30:04 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)
2025-10-18 17:28:13 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) (Ping timeout: 264 seconds)
2025-10-18 17:25:17 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 17:20:43 +0200simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 250 seconds)
2025-10-18 17:19:55 +0200Square2(~Square@user/square) Square
2025-10-18 17:17:39 +0200raym(~ray@user/raym) raym
2025-10-18 17:16:59 +0200 <geekosaur> (which is not to claim cabal's much better; you can make it work but it takes a certain amount of beating it over the head with a mallet)
2025-10-18 17:16:05 +0200 <geekosaur> more to the point, stack was designed as a (standard) ghc-specific tool, and there's about zero thought put into alternative uses such as wasm or js backend
2025-10-18 17:14:50 +0200 <geekosaur> the "right" solution is a wasm-specific snapshot, tbh, but I doubt anyone has plans to make or maintain such
2025-10-18 17:14:27 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-10-18 17:14:21 +0200 <geekosaur> right. stack isn't really intended for this
2025-10-18 17:12:35 +0200 <tabaqui> I think having an option like "load-env-from" in the stack.yaml file would suffice. However, a link from wasm32-wasi-ghc to ghc is still needed.
2025-10-18 17:09:59 +0200 <EvanR> the amount of times it comes down to having to adjust your PATH can we just stop and admit that's how to do it and stop making elaborate incompatible utilities to do it
2025-10-18 17:09:42 +0200trickard_trickard
2025-10-18 17:09:31 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 17:08:07 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) Inline
2025-10-18 17:07:41 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) (Ping timeout: 256 seconds)
2025-10-18 17:04:18 +0200 <geekosaur> I think the closest you get to that with stack is to use `system-ghc` and adjust your `PATH`
2025-10-18 17:00:53 +0200raym(~ray@user/raym) (Ping timeout: 256 seconds)
2025-10-18 16:58:37 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-10-18 16:55:09 +0200chenjf(~chenjf@68.64.178.54) (Client Quit)
2025-10-18 16:54:28 +0200chenjf(~chenjf@68.64.178.54)
2025-10-18 16:54:03 +0200 <tabaqui> What's kinda strange is that documentation for Stack.Types.DownloadInfo.url suggest using absolute path, but it is not accepted by stack build itself
2025-10-18 16:53:43 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 16:53:36 +0200chenjf(~chenjf@68.64.178.54) (Remote host closed the connection)
2025-10-18 16:52:07 +0200 <tabaqui> Hi! What is the equivalent of the cabal with-ghc option for stack? Specifically, I want to use wasm32-wasi-ghc from a different path.
2025-10-18 16:50:58 +0200tabaqui(~tabaqui@167.71.80.236) tabaqui
2025-10-18 16:43:39 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) Inline
2025-10-18 16:42:49 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)
2025-10-18 16:41:31 +0200trickard_(~trickard@cpe-57-98-47-163.wireline.com.au)
2025-10-18 16:41:17 +0200trickard(~trickard@cpe-57-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-10-18 16:37:56 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 16:35:15 +0200trickard_trickard
2025-10-18 16:31:34 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) (Read error: Connection reset by peer)
2025-10-18 16:26:34 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-10-18 16:19:53 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 16:13:38 +0200trickard_(~trickard@cpe-57-98-47-163.wireline.com.au)
2025-10-18 16:13:25 +0200trickard_(~trickard@cpe-57-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-10-18 16:08:55 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-10-18 16:04:05 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn