2025/10/07

Newest at the top

2025-10-07 21:12:15 +0200trickard(~trickard@cpe-51-98-47-163.wireline.com.au)
2025-10-07 21:12:02 +0200068AAEHYP(~trickard@cpe-51-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-10-07 21:11:50 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-07 21:09:20 +0200superstar64(~superstar@2600:1700:57e0:e3c0::31) superstar64
2025-10-07 21:07:48 +0200Guest43(~Guest43@p200300dcb74362005855840dbc960914.dip0.t-ipconnect.de) ()
2025-10-07 21:06:57 +0200 <Guest43> sm Thanks!
2025-10-07 21:05:35 +0200Guest43(~Guest43@p200300dcb74362005855840dbc960914.dip0.t-ipconnect.de)
2025-10-07 21:00:43 +0200caconym747879(~caconym@user/caconym) caconym
2025-10-07 21:00:02 +0200caconym747879(~caconym@user/caconym) (Quit: bye)
2025-10-07 20:47:31 +0200karenw(~karenw@user/karenw) (Ping timeout: 256 seconds)
2025-10-07 20:46:23 +0200 <geekosaur> I set it in my shared profile, just in case. But since it needs to know that to find its configuration, I expect it's always necessary if you want XDG
2025-10-07 20:46:13 +0200lxsameer(~lxsameer@Serene/lxsameer) lxsameer
2025-10-07 20:43:41 +0200vetkat(~vetkat@user/vetkat) vetkat
2025-10-07 20:40:43 +0200machinedgod(~machinedg@d75-159-126-101.abhsia.telus.net) (Ping timeout: 256 seconds)
2025-10-07 20:27:18 +0200Guest43(~Guest43@p200300dcb74362005855840dbc960914.dip0.t-ipconnect.de) (Quit: Client closed)
2025-10-07 20:23:51 +0200 <sm> I've not used that, but I would guess permanently
2025-10-07 20:22:50 +0200trickard__068AAEHYP
2025-10-07 20:22:49 +0200trickard(~trickard@cpe-51-98-47-163.wireline.com.au) (Ping timeout: 264 seconds)
2025-10-07 20:21:09 +0200trickard__(~trickard@cpe-51-98-47-163.wireline.com.au)
2025-10-07 20:20:02 +0200sp1ff(~user@2601:1c2:4c00:6820::1528) (Ping timeout: 256 seconds)
2025-10-07 20:19:02 +0200sp1ff`(~user@2601:1c2:4c00:6820::48ac)
2025-10-07 20:16:14 +0200 <Guest43> Thanks! And if I want to use XDG directories, do I need to set `GHCUP_USE_XDG_DIRS` permanently or only for the initial install?
2025-10-07 20:14:07 +0200tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2025-10-07 20:11:37 +0200 <sm> you can do it that way, it's fine
2025-10-07 20:09:52 +0200Everything(~Everythin@172-232-54-192.ip.linodeusercontent.com) (Quit: leaving)
2025-10-07 20:09:00 +0200 <Guest43> The thing is that I am regularly running `brew upgrade` anyway so if I didn't have to remember to run `ghcup upgrade`, that would be a plus in my opinion.
2025-10-07 20:04:58 +0200A_DragonAwoobis
2025-10-07 20:04:17 +0200A_Dragon(A_D@libera/staff/dragon) ad
2025-10-07 20:04:01 +0200A_Dragon(A_D@libera/staff/dragon) (Quit: ZNC - https://znc.in)
2025-10-07 19:58:04 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-10-07 19:54:43 +0200GdeVolpi1(~GdeVolpia@user/GdeVolpiano) GdeVolpiano
2025-10-07 19:54:11 +0200trickard__trickard
2025-10-07 19:51:43 +0200 <monochrom> I say the following to show just how "practice" and "problem" are highly personal, so no one other than you can answer that. I don't use Ubuntu's version of ghc, I choose my favourite version of ghc by using ghcup, because Ubuntu's version is usually too old for my purpose. But I just use Ubuntu's version of pandoc, and not building the latest version from hackage, because for my purpose old versions are OK.
2025-10-07 19:51:06 +0200dobblegodibblego
2025-10-07 19:51:06 +0200GdeVolpi1(~GdeVolpia@user/GdeVolpiano) (*.net *.split)
2025-10-07 19:51:06 +0200doyougnu(~doyougnu@38.175.72.111) (*.net *.split)
2025-10-07 19:51:06 +0200hc(~hc@mail.hce.li) (*.net *.split)
2025-10-07 19:51:06 +0200dibblego(~dibblego@116-255-1-119.ip4.superloop.au) (*.net *.split)
2025-10-07 19:51:06 +0200df(~ben@justworks.xyz) (*.net *.split)
2025-10-07 19:51:06 +0200gentauro(~gentauro@91.226.144.99) (*.net *.split)
2025-10-07 19:51:06 +0200gAy_Dragon(A_D@libera/staff/dragon) (*.net *.split)
2025-10-07 19:51:06 +0200vgtw(~vgtw@user/vgtw) (*.net *.split)
2025-10-07 19:50:50 +0200karenw(~karenw@user/karenw) karenw
2025-10-07 19:50:13 +0200 <sm> otherwise it's just fine
2025-10-07 19:50:09 +0200 <geekosaur> yes, but being able to select it for upgrade inside of ghcup and having it restart automatically with the new version is pretty nice. if you do that accidentally when managing the install with brew, you could break brew because what's on disk won't match what brew thinks it should be
2025-10-07 19:49:56 +0200 <sm> Guest43 it won't configure stack for you, as ghcup's curl install script would
2025-10-07 19:47:12 +0200dobblego(~dibblego@haskell/developer/dibblego) dibblego
2025-10-07 19:45:57 +0200gentauro_(~gentauro@91.226.144.99)
2025-10-07 19:45:36 +0200doyougnu-(~doyougnu@38.175.72.111)
2025-10-07 19:45:25 +0200df_(~ben@justworks.xyz)