-
Notifications
You must be signed in to change notification settings - Fork 138
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
Packages missing documentation on GHC 9.4 & 9.6 #420
Comments
I notice that in 9.4.8 & 9.6.4, the package database info uses 'pkgroot' does not appear in the hoogle codebase, so perhaps hoogle does not do the necessary string interpolation with pkgroot, resulting in the failure to find the documentation? If so, then there are 2 problems:
I suppose a deeper problem is the lack of an API/library to extract package database information. (AFAIK there is none.)
When I manually hacked the .conf files to interpolate pkgconf, the problem went away:
I suppose now one of the main questions is whose job it is to do the interpolation of pkgroot, the GHC installation procedure, ghc-pkg or tools that use ghc-pkg? |
I am also running into this and I have observed the same thing: it worked properly with |
I noticed the same thing as well. In
Also, on my 9.4.8 system, I noticed that the haddock interfaces that hoogle can find are listed as absolute paths:
This supports @jchia's theory that hoogle just isn't parsing the |
See #405 for a patch which fixes this. |
Attempting to generate database for local GHC packages fails on GHC versions 9.4.8 & 9.6.4. 9.2.8 is fine.
All the GHC versions in my tests were installed using GHCup. The
hoogle
is the latest version installed usingcabal install hoogle
.hoogle generate -l
fails to find the documentation for built-in packages likebase
andbinary
under the problematic GHC versions.hoogle generate -h
seems to find the documentation when given thehtml/libraries
directory associated with GHC installation, but the resulting database is unsuitable for serving as the generated documentation URLs have wrong paths, so-h
is not a suitable workaround.The text was updated successfully, but these errors were encountered: