2026/01/20

Newest at the top

2026-01-20 21:19:52 +0100peterbecich(~Thunderbi@71.84.33.135) (Ping timeout: 256 seconds)
2026-01-20 21:18:46 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-20 21:16:08 +0100housemate(~housemate@202.7.248.67) housemate
2026-01-20 21:13:49 +0100housemate(~housemate@202.7.248.67) (Quit: https://ineedsomeacidtocalmmedown.space/)
2026-01-20 21:09:29 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-01-20 21:07:19 +0100hakutaku(~textual@chen.yukari.eu.org) (Ping timeout: 246 seconds)
2026-01-20 21:04:54 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-20 21:02:54 +0100hakutaku(~textual@chen.yukari.eu.org)
2026-01-20 20:58:49 +0100hakutaku(~textual@chen.yukari.eu.org) (Ping timeout: 250 seconds)
2026-01-20 20:54:22 +0100 <monochrom> :)
2026-01-20 20:54:13 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2026-01-20 20:50:13 +0100 <[exa]> monochrom: ok it looks like it works just right, thanks for the hints
2026-01-20 20:49:08 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-20 20:40:47 +0100Lord_of_Life_Lord_of_Life
2026-01-20 20:40:00 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 265 seconds)
2026-01-20 20:39:27 +0100Lord_of_Life_(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2026-01-20 20:38:25 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-01-20 20:37:17 +0100Googulator58Googulator
2026-01-20 20:34:54 +0100chromoblob(~chromoblo@user/chromob1ot1c) chromoblob\0
2026-01-20 20:34:34 +0100chromoblob(~chromoblo@user/chromob1ot1c) (Read error: Connection reset by peer)
2026-01-20 20:33:20 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-20 20:31:07 +0100Googulator58(~Googulato@2a01-036d-0106-29ac-8d41-f550-2a4f-1a91.pool6.digikabel.hu)
2026-01-20 20:31:06 +0100 <[exa]> --force-reinstall has some scary extra package-breaking semantics
2026-01-20 20:30:51 +0100Googulator58(~Googulato@2a01-036d-0106-29ac-8d41-f550-2a4f-1a91.pool6.digikabel.hu) (Quit: Client closed)
2026-01-20 20:30:49 +0100 <[exa]> ok --dry-run --reinstall and then diffing it kinda seems to work
2026-01-20 20:30:23 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2026-01-20 20:28:22 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...)
2026-01-20 20:28:12 +0100 <monochrom> maybe --force-reinstall helps
2026-01-20 20:26:51 +0100 <[exa]> y e a h. :D
2026-01-20 20:26:29 +0100 <monochrom> "When confronted with a problem to be solved by a shell script, some people say, 'I know, I will run it in docker'. Now they have two problems." :)
2026-01-20 20:26:02 +0100newmind(~newmind@91-133-90-252.dyn.cablelink.at) (Quit: Client closed)
2026-01-20 20:25:30 +0100 <monochrom> But then maybe you can do that inside a docker container that starts clean. >:)
2026-01-20 20:25:06 +0100 <monochrom> But then you have to set it back to the default after you're done.
2026-01-20 20:24:59 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-01-20 20:24:54 +0100peterbecich(~Thunderbi@71.84.33.135) peterbecich
2026-01-20 20:24:26 +0100 <monochrom> In $HOME/.cabal/config, you can set a non-default store-dir, then it's like restarting from scratch (if you set it to an empty directory).
2026-01-20 20:24:11 +0100Lycurgus(~juan@user/Lycurgus) Lycurgus
2026-01-20 20:22:38 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2026-01-20 20:19:17 +0100 <monochrom> OK, my next idea is to actually install lens (as an example), then I use my own program to show the complete (except for what comes with GHC) tree, "cabalgc --deps lens"
2026-01-20 20:18:15 +0100 <[exa]> b/c then I can compute the difference manually
2026-01-20 20:18:06 +0100 <[exa]> oh wait can I somehow just list all transitive dependencies of a package?
2026-01-20 20:17:45 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-20 20:17:28 +0100 <[exa]> yeah running cabal will usually soak in some environment (I guess I could isolate it, right?)
2026-01-20 20:16:33 +0100 <monochrom> Ah, the problem is if I already have built a depended-on package, it won't be on the list.
2026-01-20 20:15:19 +0100 <monochrom> "cabal repl --dry-run x.hs" where x.hs contains "depends: base, lens"
2026-01-20 20:14:49 +0100 <monochrom> or the "cabal script" equivalent
2026-01-20 20:14:31 +0100 <monochrom> I just do "cabal install --lib --dry-run lens"
2026-01-20 20:13:33 +0100FloorCalc(~user@user/FloorCalc) (Quit: toodles)
2026-01-20 20:10:57 +0100 <[exa]> Is there some nice tool to collect/visualize the relations between package dependencies? e.g., I want to add a dependency to a package and wonder if it's going to pull a gazillion of other indirect deps or not (e.g. because they're already pulled in by the original package). Ideally other than "try with cabal", I'd love to have this in some kind of a script.
2026-01-20 20:10:10 +0100notzmv(~umar@user/notzmv) notzmv