[Hackage] #402: Automatic hoogle database for installed packages
#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 | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ The hoogle package is very useful to search the standard library. Unfortunately, it does not search packages that you have installed which are not part of the stdlib. It would be great if every package installed always had its haddock generated, and from its .txt file a .hoo file was generated (e.g: hoogle --convert), and then all .hoo files sat in some centralized directory which hoogle would then use for its searches. This would be great documentation, and let you hoogle for anything that you can import. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/402 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#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 Peaker): Using hoogle --convert on the .txt files directly will not work until this bug is fixed: http://hackage.haskell.org/trac/ghc/ticket/2766 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/402#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#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: ---------------------------------+------------------------------------------ Changes (by guest): * cc: gwern0@gmail.com (added) Comment: #3766 has been fixed. More importantly, I'm not sure it was a problem. I'm still on 6.10.1, but my Hoogle had no problem converting an xmonad-contrib.txt and searching the .hoo file. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/402#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#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: ---------------------------------+------------------------------------------ Changes (by guest): * cc: ndmitchell@gmail.com (added) Comment: #3766 would only have been a problem for certain libraries, so it won't effect most things. This would be great if someone could do it :-) I'll do any Hoogle changes that are necessary, but don't have time to do the Cabal side. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/402#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#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
participants (1)
-
Hackage