#402: Automatic hoogle database for installed packages ---------------------------------+------------------------------------------ Reporter: Peaker | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.8.3 | Platform: ---------------------------------+------------------------------------------ Comment (by guest): I don't think many Hoogle changes are necessary, but it's unclear how it's going to be handled. Is Cabal going to dump .hoo files into Hoogle's data- directory, or should Hoogle be going and looking elsewhere for .hoo files or what? Personally, I like the idea of Cabal dumping the generated .hoo file into Cabal's data-directory myself. Simple. But that opens other questions. As ndm says, 'Hoogle could look in the same directory as haddock does for its documentation databases, Hoogle could dump its path to stdout, hoogle could dump the converted files to its path'. Here again I favor the simple solution of dumping the path to stdout, but another possibility is exposing Hoogle's library and thus Paths_hoogle (I think that'd work). Finally, there becomes the question of what .hoos Hoogle should look in by default. ndm: "There should certainly be an all database, and an all libraries on hackage database, and an all installed libraries database. Which one of those is default is a good question, I'd guess at all installed libraries - but not certain." -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/402#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects