Newest at the top
| 2025-10-30 22:49:11 +0100 | nerdychip | (~nerdychip@user/nerdychip) (Read error: Connection reset by peer) |
| 2025-10-30 22:46:25 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds) |
| 2025-10-30 22:44:51 +0100 | michalz | (~michalz@185.246.207.221) (Remote host closed the connection) |
| 2025-10-30 22:44:35 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Read error: Connection timed out) |
| 2025-10-30 22:41:26 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-30 22:35:44 +0100 | Googulator97 | (~Googulato@2a01-036d-0106-03fa-9dbb-a0af-2124-a319.pool6.digikabel.hu) |
| 2025-10-30 22:35:30 +0100 | Googulator97 | (~Googulato@2a01-036d-0106-03fa-9dbb-a0af-2124-a319.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-10-30 22:34:20 +0100 | haltingsolver | (~cmo@2604:3d09:207f:8000:d250:ea0c:366a:6e73) |
| 2025-10-30 22:32:24 +0100 | haltingsolver | (~cmo@2604:3d09:207f:8000::d1dc) (Ping timeout: 256 seconds) |
| 2025-10-30 22:30:42 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-10-30 22:25:39 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-30 22:21:25 +0100 | nerdychip | (~nerdychip@user/nerdychip) nerdychip |
| 2025-10-30 22:21:25 +0100 | nerdychip | (~nerdychip@212.129.72.100) (Changing host) |
| 2025-10-30 22:21:25 +0100 | nerdychip | (~nerdychip@212.129.72.100) |
| 2025-10-30 22:20:45 +0100 | <haskellbridge> | <sm> 2020 intel thinkpad possibly swapping |
| 2025-10-30 22:19:55 +0100 | peterbecich | (~Thunderbi@172.222.148.214) (Ping timeout: 256 seconds) |
| 2025-10-30 22:19:06 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Quit: ljdarj) |
| 2025-10-30 22:18:41 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-10-30 22:18:34 +0100 | nerdychip | (~nerdychip@user/nerdychip) (Read error: Connection reset by peer) |
| 2025-10-30 22:16:18 +0100 | Googulator97 | (~Googulato@2a01-036d-0106-03fa-9dbb-a0af-2124-a319.pool6.digikabel.hu) |
| 2025-10-30 22:16:09 +0100 | Googulator97 | (~Googulato@2a01-036d-0106-03fa-9dbb-a0af-2124-a319.pool6.digikabel.hu) (Client Quit) |
| 2025-10-30 22:16:08 +0100 | Googulator29 | (~Googulato@2a01-036d-0106-03fa-9dbb-a0af-2124-a319.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-10-30 22:15:45 +0100 | <davean> | omentic: BTW what makes build times so bad for you? (I didn't read up) |
| 2025-10-30 22:15:40 +0100 | Googulator97 | (~Googulato@2a01-036d-0106-03fa-9dbb-a0af-2124-a319.pool6.digikabel.hu) |
| 2025-10-30 22:15:17 +0100 | <omentic> | thx for the help here yall |
| 2025-10-30 22:15:05 +0100 | <omentic> | well, i'll try to fix the parallelism, then try to get caching working, but i'll have to do it a bit later |
| 2025-10-30 22:15:02 +0100 | <davean> | and if you're layering it on top of stackage, the size explosion isn't so bad |
| 2025-10-30 22:14:51 +0100 | <davean> | You CAN build this cache |
| 2025-10-30 22:14:36 +0100 | <omentic> | interesting ok |
| 2025-10-30 22:13:54 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-30 22:12:07 +0100 | <davean> | I think a *binary result equality match* I THINK but I'm not sure there |
| 2025-10-30 22:11:48 +0100 | <davean> | but it needs an equality match |
| 2025-10-30 22:11:42 +0100 | <davean> | so it only needs the dependencies of pandoc and your overall project to match |
| 2025-10-30 22:11:26 +0100 | <davean> | GHC works with a consistent set of dependencies |
| 2025-10-30 22:11:06 +0100 | <omentic> | but also from what you said earlier sounds like ghc needs all dependencies and such for the compiler to do its thing |
| 2025-10-30 22:11:00 +0100 | <davean> | It can be specific to a given install of an os |
| 2025-10-30 22:10:24 +0100 | <davean> | Thats not enough, thats just enough MOST of the time |
| 2025-10-30 22:10:07 +0100 | <omentic> | oh yeah that tracks. but your distinction for a cache would be by cpu architecture + os, right |
| 2025-10-30 22:10:05 +0100 | <davean> | Like its not actually that much of a deal for most users |
| 2025-10-30 22:09:33 +0100 | <davean> | no I'm talking about a cache |
| 2025-10-30 22:09:19 +0100 | <omentic> | i'm surprised that breaks -j |
| 2025-10-30 22:09:06 +0100 | <davean> | omentic: very specificly POSIX is a source code level compatability standard, not a binary compatability standard, and distros can and do break binary compatability between them, and some even inside them. |
| 2025-10-30 22:07:59 +0100 | <monochrom> | Hell even Thunderbird and Firefox probably don't use each other's cache... |
| 2025-10-30 22:07:29 +0100 | <monochrom> | I don't know how to tell cabal to use stack's cache, or stack to use cabal's cache. |
| 2025-10-30 22:07:12 +0100 | <davean> | You can only cache it in respect to the otehr things you build so I'm nto sure what the use would be |
| 2025-10-30 22:06:51 +0100 | <davean> | and then sometimes, rarely but it will happen, it'll spit out a binary that doesn't work |
| 2025-10-30 22:06:48 +0100 | <omentic> | do you know if it is possible to get a partial cache? i.e. cache pandoc but not cache the other dependency i need. or is this impossible wrt. how ghc builds things |
| 2025-10-30 22:06:19 +0100 | <davean> | So anyway, no one actively provides such a cache for cabal+hackage in general. Its not hard to do but it would be very large. |
| 2025-10-30 22:05:55 +0100 | <davean> | but yah |
| 2025-10-30 22:05:53 +0100 | <davean> | er, not stackage |