2025/03/16

Newest at the top

2025-03-16 23:34:28 +0100 <mauke> davean: what standards are you talking about?
2025-03-16 23:31:01 +0100jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 244 seconds)
2025-03-16 23:30:49 +0100MyNetAz(~MyNetAz@user/MyNetAz) (Remote host closed the connection)
2025-03-16 23:24:49 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 244 seconds)
2025-03-16 23:10:05 +0100 <davean> Also, frankly, I doubt anyone keeps the GNU style guide one.
2025-03-16 23:09:31 +0100 <davean> Well, specificly 2, but you can tell them appart by file name.
2025-03-16 23:08:30 +0100jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-03-16 23:06:26 +0100 <davean> Yes but there *is* infact a standard
2025-03-16 23:05:42 +0100mange(~user@user/mange) mange
2025-03-16 23:05:40 +0100 <geekosaur> I think the main complaint would be that it would require cabal to impose some structure on changelogs so it could recognize whether it was there or not
2025-03-16 23:03:59 +0100 <davean> Its a good warning
2025-03-16 23:03:54 +0100 <davean> It seems worse to have it as a local thing for just yourself.
2025-03-16 23:03:36 +0100 <davean> mauke: why not contribute it back as a warning for everyone?
2025-03-16 23:01:14 +0100 <geekosaur> (external commands are implemented but there's not currently a plan for extending existing ones)
2025-03-16 23:00:44 +0100 <geekosaur> starting to happen but not there yet
2025-03-16 22:57:54 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 260 seconds)
2025-03-16 22:53:31 +0100myme(~myme@40.51-175-185.customer.lyse.net) (Ping timeout: 244 seconds)
2025-03-16 22:53:07 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-16 22:50:26 +0100 <mauke> I was hoping cabal would be extensible
2025-03-16 22:48:48 +0100 <davean> That is outside the default scope for check, its clearly a warning level feature though
2025-03-16 22:48:15 +0100 <davean> mauke: you tell it by adding the code there :)
2025-03-16 22:48:13 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Quit: installing updates)
2025-03-16 22:45:10 +0100 <mauke> :-(
2025-03-16 22:43:14 +0100 <merijn> mauke: Not sure it can do that?
2025-03-16 22:32:18 +0100MyNetAz(~MyNetAz@user/MyNetAz) MyNetAz
2025-03-16 22:27:46 +0100DigitteknohippieDigit
2025-03-16 22:27:13 +0100 <mauke> ?
2025-03-16 22:25:51 +0100 <davean> https://github.com/haskell/cabal/blob/d93f06606cef7ff1df24c88488a9a706e5af770f/cabal-install/src/D…
2025-03-16 22:25:21 +0100xatirig(~xatirig@81.215.239.1)
2025-03-16 22:22:24 +0100 <mauke> how do I tell 'cabal check' to verify that my changelog contains an entry for the current version?
2025-03-16 22:21:09 +0100 <mauke> haha
2025-03-16 22:20:28 +0100 <merijn> like, yesterday
2025-03-16 22:20:20 +0100 <merijn> mauke: I only discovered due to modern cabal's warning about it xD
2025-03-16 22:20:11 +0100halloy7351(~halloy735@81.215.239.1) (Quit: halloy7351)
2025-03-16 22:20:08 +0100 <merijn> mauke: Same ;)
2025-03-16 22:19:37 +0100 <mauke> love discovering cutting edge features from 2013
2025-03-16 22:19:14 +0100halloy7351(~halloy735@81.215.239.1)
2025-03-16 22:18:05 +0100 <merijn> extra-doc-files do not
2025-03-16 22:18:03 +0100 <mauke> yeah, just found that
2025-03-16 22:17:54 +0100 <merijn> mauke: The one thing that should easily clinch the argument for you: extra-source-file changes invalidate the build cache
2025-03-16 22:17:30 +0100 <merijn> mauke: extra-source-file predates extra-doc-file (which wasn't really popularised enough)
2025-03-16 22:17:07 +0100 <merijn> extra-doc-file
2025-03-16 22:17:06 +0100 <mauke> prior art seems split on this point
2025-03-16 22:16:58 +0100 <mauke> is a changelog an extra-source-file or an extra-doc-file?
2025-03-16 22:14:42 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2025-03-16 22:11:56 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-03-16 22:11:19 +0100MyNetAz(~MyNetAz@user/MyNetAz) (Remote host closed the connection)
2025-03-16 22:10:28 +0100 <c_wraith> it's just not implemented with the non-threaded runtime. I suggested an implementation and was told "that's a feature request, not a bug"
2025-03-16 22:09:46 +0100 <merijn> oof
2025-03-16 22:09:29 +0100 <c_wraith> merijn: https://hackage.haskell.org/package/stm-2.5.3.1/docs/Control-Concurrent-STM-TVar.html#v:registerDe…