hoogling GHC

Ranjit Jhala jhala at cs.ucsd.edu
Mon Mar 14 20:37:14 CET 2011

Hi Neil -- 

Is there a command line option that allows one to change the default prefix for the 
URL returned by searches?

For example, I managed to get a local hoogle server to index over ghc.foo but a 
query "dfun" returned the (dead) link


presumably using the default prefix for hackage.haskell.org/... 
Instead, by manually tweaking the prefix to


I get something useful. Is there some way to rig the .txt --> .foo conversion to use
a manually supplied prefix?

Thanks for your help with this!


On Mar 9, 2011, at 1:59 PM, Neil Mitchell wrote:

> Hi Ranjit,
> It sounds like you've got quite far. Sadly the manual is a bit out of
> date with respect to generating databases, but generally you need to
> produce ghc.txt on your own (using tools such as GHC's make system),
> then you can do:
> hoogle convert ghc.txt default.hoo
> Then you can run the local server with:
> hoogle server --databases=.
> That will find databases from the current directory, and serve them.
> Alternatively, if you put ghc.hoo (or default.hoo) in
> $DATADIR/databases it will pick them up automatically (where $DATADIR
> is whatever Cabal configured it to be). If you name the database as
> default.hoo it will be searched by default, if you name it ghc.hoo
> then "foo +ghc" will search for foo in the GHC database.
> If a copy of ghc.txt was publicly available somewhere (and updated on
> some schedule), I'd be happy to make the official Hoogle server search
> it. Usually I just grab databases off Hackage, but I'll happily make
> an exception for GHC.
> Thanks, Neil
> On Sun, Mar 6, 2011 at 7:52 AM, Malcolm Wallace <malcolm.wallace at me.com> wrote:
>>> The final stumbling block is getting the local webserver (hoogle server)
>>> to also search the above database. I'm sure there must be some simple way
>>> I
>>> can pass the name of the database as an argument when I boot up the
>>> server,
>>> but I can't seem to find it...
>> Have you found the various versions of the web deployment procedure yet?
>> deploy.txt:  instructions to follow manually (seems to be up-to-date)
>> deploy.sh:   a shell script version to run locally (may be old)
>> Deploy.hs:   a haskell version to run remotely (may also be old)
>> Obviously those scripts are tailored to the official installation, but there
>> are some clues in there, for instance the steps
>>    cabal configure --datadir=/srv/web/haskell.org/hoogle/
>> --datasubdir=datadir -O2
>> and
>>    Upload datadir/resources to /srv/web/haskell.org/hoogle/datadir/resources
>>    Upload datadir/databases/* to
>> /srv/web/haskell.org/hoogle/datadir/databases
>> Regards,
>>    Malcolm
>> _______________________________________________
>> Glasgow-haskell-users mailing list
>> Glasgow-haskell-users at haskell.org
>> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

More information about the Glasgow-haskell-users mailing list