Closed blitzcode closed 10 years ago
I have a suspicion that you have to type hoogle data all default
. I agree, that's an absolutely terrible (and unpredictable) interface. More annoyingly, if you type hoogle data all && hoogle data all default
it will rebuild all packages twice. That's pretty crazy. I'm reworking all the package stuff at the moment, so I'll definitely keep this in mind. For the moment, I suggest either hoogle data all && hoogle data default
or hoogle data all default
to get what you want.
Thanks for the quick reply, I must've totally missed that 'default' flag!
I tried finding it in the source without success, but can you tell me which database I have add to my default.hoo to get all hackage package names included in the search?
The package.hoo
database contains names of all the packages.
Thank you!
I updated my personal notes on how to install & setup a local Hoggle, maybe it's of help to somebody else stumbling on this bug report:
I've just fixed this, so now all
implies default
. I've also added a -j
flag so you can parallelise the creation of databases, which I imagine you will want to use with hoogle data all
.
Oh, nice! 'data all' takes a while, so this is certainly helpful.
Looks like we're not getting a -j for GHC this year, but having it for Cabal and last-minute for Hoogle softens the blow! ;-)
Hoogle will also be getting incremental builds quite shortly (#49), so if you don't upgrade Hoogle and just download fresh data from Hackage (the --redownload
flag), you will hopefully have a few minutes to update all, instead of having to regenerate it all as now. I also want to make it faster to generate from scratch. Most of these improvements are necessary to keep updating the haskell.org version every day without burning too much CPU, but they'll also be useful to people doing it locally.
The last couple of times I installed Hoogle 4.2.26 and ran 'hoogle data all' the default.hoo was missing from the database. All individual packages are there, and building it myself with 'hoogle combine' works out fine, but it renders Hoogle non-operable out of the box.