-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new-haddock can't produce documentation suitable for Hackage? #5341
Comments
I think |
@alexbiehl ...do you remember what's missing here? did we ever create a ticket about lazy haddocking? |
I think this works in HEAD or one of Alex's branches, since I've successfully build and uploaded Hackage docs using new-haddock 1 or 2 months ago when he was working on that. To the best of my knowledge it's still broken in the last released cabal-install? @RyanGlScott are you using cabal-install HEAD or older? |
I'd say that this is fixed after #5395, since I can now run:
And it will build suitable-for-Hackage Haddocks, building dependencies with documentation enabled if need be. |
I'm not sure if this is expected behavior or not, but it's certainly throwing me for a loop. I occasionally need to upload Haddocks to Hackage manually. With old-style
cabal
, my usual workflow would be:--enable-documentation
on.cabal haddock --for-hackage
.cabal upload -d <doc-tarball> --publish
I'm trying to figure out how to emulate this workflow with
new-haddock
, but it doesn't seem to be quite up to the task. My first inclination was to try this:However, this did not build my dependencies with documentation enabled. It simply built the package itself (using previously built versions of the dependencies, without documentation) and ran Haddock on the package, and unsurprisingly, that resulted in unbound link destinations:
Passing
--haddock-for-hackage
didn't seem to help either.I also tried directly invoking
cabal new-haddock --haddock-for-hackage
, but that too did not build the dependencies with documentation enabled.The text was updated successfully, but these errors were encountered: