| 19 May 2025 |
 keypusher | none of doc/docs/documentation seems to do it | 19:55:23 |
 maralorn | When I build e.g. nixpkgs#haskellPackages.aeson.doc I get the docs in a symlink called result-doc. | 19:57:31 |
| keypusher | ah ok | 19:58:58 |
| maralorn | Found them? | 19:59:31 |
| keypusher | I build with nix flake build and the only output I get is the result symlink that countains lib and bin | 20:01:28 |
| maralorn | And if you build nix build .#default.doc? | 20:05:17 |
| keypusher | I'll try after i adopt the change about overrideCabal you proposed. | 20:06:12 |
| maralorn | Alternatively there is this absurd syntax: nix build '.#default^*' which will build all outputs. | 20:06:50 |
| keypusher | hehe. Worth a try | 20:07:09 |
| keypusher | tried nix build --impure --print-build-logs .#default.doc | 20:09:41 |
| keypusher | It produced a result-doc symlink... but the folder was empty | 20:10:05 |
| maralorn | heh | 20:12:09 |
| keypusher | Maybe the problem isn't a nix one but that i haven't configured haddock properly?! I have to confess I rarely produce docs. | 20:12:55 |
| maralorn | Just to be sure can you do readlink result-doc? | 20:13:08 |
| maralorn | It seems to be something like that, but you normally don’t have to do anything to have haddocks enabled. | 20:13:54 |
| maralorn | Which plattform are you on? | 20:14:03 |
| maralorn | * Which platform are you on? | 20:14:08 |
| keypusher | Seems to work | 20:14:08 |
| maralorn | does it end in something like <hash>-lf-regstry3-<version>-doc? | 20:15:11 |
| maralorn | * does it end in something like <hash>-lf-registry3-<version>-doc? | 20:15:21 |
| keypusher | x86-linux | 20:15:54 |
| keypusher | output: /nix/store/j4s4pxm1wmdgd5s14xlbmkc57fcrha60-RegistryThree-0.1.2.0-doc | 20:16:24 |
| maralorn | Looks good. | 20:16:37 |
| maralorn | Can you maybe rerun the build e.g. with nix build --print-build-logs .#default.doc and have a look for the haddockPhase being mentioned in the logs? | 20:17:19 |
| maralorn | * Can you maybe rerun the build e.g. with nix build --check --print-build-logs .#default.doc and have a look for the haddockPhase being mentioned in the logs? | 20:17:27 |
| keypusher | Jumped into a shell and did "cabal haddock", which does produce a documentation | 20:17:40 |
| maralorn | Huh, I guess you don’t even need to rerun it. | 20:17:42 |
| maralorn | You can do something like nix log .#default.doc I think. | 20:18:00 |
| keypusher | ok | 20:18:12 |
| keypusher | unrecognized flag "--check" ? | 20:19:32 |
