You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running a local instance of Hoogle (via Nix) with my employer's packages and their dependencies. I've always noticed that hoogle.haskell.org has a more logical order for packages when there are multiple hits (ie preferring base). After some searching, I found that this is probably because of a difference in ReorderModule rules. I also see there exists a misc/settings.txt, but I don't know how to supply this file myself or why the default rules result in a different order compared to hoogle.haskell.org.
The text was updated successfully, but these errors were encountered:
let backup =$(runIO (readFileUTF8 "misc/settings.txt") >>= lift)
- it's a Cabal data file. So simply doing cabal install should cause it to see the settings.txt file that ships with Hoogle. Are you running Hoogle from a cabal package or from the repo?
We are using this Nix derivation to generate a Hoogle database for our own packages and their dependencies. It receives the hoogle package that is packaged in nixpkgs as input, which I believe is built using cabal.
I'm running a local instance of Hoogle (via Nix) with my employer's packages and their dependencies. I've always noticed that hoogle.haskell.org has a more logical order for packages when there are multiple hits (ie preferring
base
). After some searching, I found that this is probably because of a difference inReorderModule
rules. I also see there exists amisc/settings.txt
, but I don't know how to supply this file myself or why the default rules result in a different order compared to hoogle.haskell.org.The text was updated successfully, but these errors were encountered: