Newest at the top
| 2026-05-26 02:25:18 +0000 | merijn | (~merijn@62.45.136.136) (Ping timeout: 252 seconds) |
| 2026-05-26 02:23:25 +0000 | Garbanzo | (~Garbanzo@2602:304:6eac:dc10::49) |
| 2026-05-26 02:20:10 +0000 | merijn | (~merijn@62.45.136.136) merijn |
| 2026-05-26 02:14:18 +0000 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 252 seconds) |
| 2026-05-26 02:12:00 +0000 | Square | (~Square@user/square) (Ping timeout: 263 seconds) |
| 2026-05-26 02:09:19 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-05-26 02:07:44 +0000 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) |
| 2026-05-26 02:05:37 +0000 | prdak | (~Thunderbi@user/prdak) (Ping timeout: 272 seconds) |
| 2026-05-26 02:04:22 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-26 01:53:22 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-05-26 01:49:25 +0000 | Square | (~Square@user/square) Square |
| 2026-05-26 01:48:37 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-26 01:46:13 +0000 | Square2 | (~Square4@user/square) (Remote host closed the connection) |
| 2026-05-26 01:39:13 +0000 | polykernel | (~polykerne@user/polykernel) (Ping timeout: 276 seconds) |
| 2026-05-26 01:38:02 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 262 seconds) |
| 2026-05-26 01:33:14 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-26 01:32:49 +0000 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 245 seconds) |
| 2026-05-26 01:26:24 +0000 | <monochrom> | Even ".there-is-no-cabal" would have worked great. |
| 2026-05-26 01:24:47 +0000 | cyclemaniac | (~cyclemani@2a02:8071:881:2d20:c1c7:793e:b89b:1589) (Ping timeout: 245 seconds) |
| 2026-05-26 01:24:34 +0000 | <monochrom> | How would they miss the opportunity of ".cabal-secret" back then? >:) |
| 2026-05-26 01:24:18 +0000 | <geekosaur> | I kinda feel like it might have been better to use the same convention as local project config and freeze file |
| 2026-05-26 01:23:19 +0000 | <geekosaur> | I do think "dist-newstyle" is a fairly lousy name though because it's not really. (it's project , whereas "dist" is package ) |
| 2026-05-26 01:22:09 +0000 | <monochrom> | Also consider "nix-style nix integration" just for fun >:) |
| 2026-05-26 01:22:03 +0000 | <geekosaur> | there's some others, but at least some are broken because they weren't updated when XDG support was added |
| 2026-05-26 01:20:39 +0000 | acidjnk_new | (~acidjnk@p200300d6e700e587d0d964644d901e6e.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) |
| 2026-05-26 01:20:35 +0000 | <monochrom> | Then again probably only cabal-plan needs it. |
| 2026-05-26 01:20:24 +0000 | merijn | (~merijn@62.45.136.136) (Ping timeout: 252 seconds) |
| 2026-05-26 01:19:59 +0000 | <monochrom> | cabal-plan is probably one program that currently assumes "dist-newstyle" and needs to know the new setting |
| 2026-05-26 01:19:05 +0000 | <monochrom> | Well yeah like some of the comments say, changing it now after all these years break backward compatibility unless configurable with traditional default. |
| 2026-05-26 01:17:41 +0000 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2026-05-26 01:16:13 +0000 | <jj> | monochrom: https://github.com/haskell/cabal/issues/5731 |
| 2026-05-26 01:16:10 +0000 | peterbecich | (~Thunderbi@71.84.33.135) peterbecich |
| 2026-05-26 01:15:41 +0000 | <monochrom> | There has never been any RFC about accurate names. |
| 2026-05-26 01:15:33 +0000 | <geekosaur> | Also "nix-style" is gradually going away because it confuses people into thinking Nix is involved or even required |
| 2026-05-26 01:15:19 +0000 | merijn | (~merijn@62.45.136.136) merijn |
| 2026-05-26 01:15:08 +0000 | <monochrom> | But you have never had that problem because you have only one project for now. |
| 2026-05-26 01:14:50 +0000 | <jj> | ah, there is a closed rfc about naming this literally anything other than dist-newstyle lmfao. rip |
| 2026-05-26 01:14:44 +0000 | <monochrom> | It is a footgun to have two projects use the same directory. |
| 2026-05-26 01:14:20 +0000 | <jj> | absolute path appears to work fine |
| 2026-05-26 01:13:51 +0000 | <geekosaur> | It's too big a footgun |
| 2026-05-26 01:13:30 +0000 | <geekosaur> | Actually I'm expecting that giving it an absolute path would raise an error |
| 2026-05-26 01:12:51 +0000 | <monochrom> | I don't know how to cofig this because I never felt the need to because I have long been disillusioned about "meaningful" names. |
| 2026-05-26 01:12:24 +0000 | <jj> | newstyle, nix-style, v2-style... an unfortunate abundance of names |
| 2026-05-26 01:11:52 +0000 | <jj> | do yall know of any option to set distdir in a .cabal file? |
| 2026-05-26 01:11:25 +0000 | <jj> | that is what i mean, but i think geekosaur probably is hinting at that --distdir can take absolute paths |
| 2026-05-26 01:10:30 +0000 | <monochrom> | geekosaur, I now think that jj means that if $HOME/.cabal/config could accept a setting like "distdir: foo" then every project would have a foo instead of a dist-newstyle. |
| 2026-05-26 01:09:03 +0000 | xff0x | (~xff0x@2405:6580:b080:900:5801:469a:d89d:a8ee) (Ping timeout: 246 seconds) |
| 2026-05-26 01:08:32 +0000 | <monochrom> | "dist" was taken. by v1. |
| 2026-05-26 01:08:22 +0000 | <geekosaur> | There isn't because every project would use that directory and they'll conflict with each other |
| 2026-05-26 01:07:50 +0000 | <jj> | it's not very evocative of what it does. i'd rather it be called dist or target or _output or something hidden. |