Newest at the top
| 2025-03-16 18:53:09 +0100 | <merijn> | I already tried that, but as usual it lies to me |
| 2025-03-16 18:51:36 +0100 | ash3en | (~Thunderbi@89.56.182.235) (Quit: ash3en) |
| 2025-03-16 18:50:51 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) |
| 2025-03-16 18:50:49 +0100 | <EvanR> | upgrade to chatGPT |
| 2025-03-16 18:50:42 +0100 | <EvanR> | google smh |
| 2025-03-16 18:47:05 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-03-16 18:45:51 +0100 | <merijn> | I'm sure *someone* has succesfully done this, but google is only turning up uselessly out of date result or results for the wrong topic |
| 2025-03-16 18:45:20 +0100 | Digit | (~user@user/digit) (Ping timeout: 252 seconds) |
| 2025-03-16 18:45:10 +0100 | <merijn> | hmmm, manually fixing up the haddock file still doesn't seem to work. At least, the docs aren't visible on the hackage candidate |
| 2025-03-16 18:44:00 +0100 | Digitteknohippie | (~user@user/digit) Digit |
| 2025-03-16 18:42:10 +0100 | Pixi | (~Pixi@user/pixi) (Read error: Connection reset by peer) |
| 2025-03-16 18:34:57 +0100 | <merijn> | anyone know what the txt file that `cabal haddock` generates is? Is it just a text representation of the documentation? If yes, how do I stop it from generating that, since it breaks things |
| 2025-03-16 18:26:24 +0100 | notdabs | (~Owner@2600:1700:69cf:9000:8c4a:1bad:bb61:8f8d) |
| 2025-03-16 18:26:01 +0100 | notdabs | (~Owner@2600:1700:69cf:9000:8c4a:1bad:bb61:8f8d) (Remote host closed the connection) |
| 2025-03-16 18:23:30 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 248 seconds) |
| 2025-03-16 18:21:13 +0100 | <merijn> | It also still includes file names that cause hackage to reject them |
| 2025-03-16 18:21:04 +0100 | ash3en | (~Thunderbi@89.56.182.235) ash3en |
| 2025-03-16 18:20:49 +0100 | <merijn> | I have 3 library components and it seems to build docs for each and then write them out to the exact same path making it a race which docs you actually get |
| 2025-03-16 18:20:08 +0100 | <merijn> | geekosaur: That does not seem fixed in HEAD |
| 2025-03-16 18:19:21 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-16 18:16:01 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-03-16 18:13:47 +0100 | user363627 | (~user@user/user363627) (Remote host closed the connection) |
| 2025-03-16 18:12:32 +0100 | <merijn> | I've been waiting for this glorious moment since, like, 2019 :p |
| 2025-03-16 18:11:57 +0100 | <merijn> | because the gain from merging this back into 1 package is too great to postpone this over doc generation :p |
| 2025-03-16 18:11:48 +0100 | <geekosaur> | https://github.com/haskell/cabal/blob/master/README.md#preview-releases |
| 2025-03-16 18:11:28 +0100 | <merijn> | lemme try that |
| 2025-03-16 18:11:07 +0100 | <geekosaur> | right |
| 2025-03-16 18:09:49 +0100 | <merijn> | So if I try cabal-install HEAD it might work? |
| 2025-03-16 18:08:15 +0100 | <geekosaur> | I think master has at least a partial fix that should be in 3.14.2.0 |
| 2025-03-16 18:08:11 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) wootehfoot |
| 2025-03-16 18:07:51 +0100 | <geekosaur> | there's still some issues with sublibraries and docs |
| 2025-03-16 18:07:39 +0100 | <geekosaur> | that's a known bug |
| 2025-03-16 18:05:38 +0100 | <merijn> | hmmm, seems it just has docs for the last build sub-library. Can I just naively combine the tar files for each sub-library to get one with everything? |
| 2025-03-16 18:00:11 +0100 | manwithluck | (~manwithlu@2a09:bac1:5ba0:20::49:217) manwithluck |
| 2025-03-16 17:57:14 +0100 | <merijn> | I'm so confused, I *see* it building docs for all libraries in the shell output, but only one seems to end up in the final tarball? |
| 2025-03-16 17:53:46 +0100 | tv | (~tv@user/tv) tv |
| 2025-03-16 17:52:31 +0100 | Square2 | (~Square4@user/square) Square |
| 2025-03-16 17:51:48 +0100 | <merijn> | I tried to naively just do `cabal haddock --haddock-for-hackage`, but that seems broken |
| 2025-03-16 17:51:25 +0100 | <merijn> | Is there some different/new invocation for haddock that I need to use for multi-library packages? |
| 2025-03-16 17:49:41 +0100 | <merijn> | It seems to have only build documentation for a single sub library and uses a naming format that's not legal on windows |
| 2025-03-16 17:48:48 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 264 seconds) |
| 2025-03-16 17:48:44 +0100 | <merijn> | hmm, the entire doc output seems to be garbage |
| 2025-03-16 17:48:37 +0100 | dhil | (~dhil@2a0c:b381:52e:3600:51d8:861d:bb57:d7c1) (Ping timeout: 268 seconds) |
| 2025-03-16 17:46:55 +0100 | <merijn> | "broadcast-chan-0.3.0-docs\\conduit\\broadcast-chan:conduit.txt" |
| 2025-03-16 17:46:55 +0100 | <merijn> | Invalid windows file name in tar archive: |
| 2025-03-16 17:45:38 +0100 | <merijn> | I'm trying to manually upload docs for my library, but it barfs on containing a file with a path that's not legal on windows |
| 2025-03-16 17:45:07 +0100 | <merijn> | Seems like someone made a think-o |
| 2025-03-16 17:44:53 +0100 | <merijn> | hmm |
| 2025-03-16 17:44:33 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 244 seconds) |
| 2025-03-16 17:42:00 +0100 | kuribas` | (~user@ptr-17d51emrd94iart11eg.18120a2.ip6.access.telenet.be) (Ping timeout: 276 seconds) |