Exposed module still hidden, why?
J. Garrett Morris
trevion at gmail.com
Tue Nov 20 15:31:39 EST 2007
As I understand it, Cabal hides all packages by default. If a package
is not in your dependencies, it won't be available to the build, no
matter the status in ghc-pkg.
(Incidentally, this had neat consequences in the past, since it means
that packages being hidden in ghc-pkg also does not make them
unavailable to cabal. I spent some time at a previous employer
attempt to debug a build failure where it turned out that the
developer experiencing the failure had not pulled all the changes. In
particular, we had packages A, B, and C, where C depended on A and B,
and B depended on A. The developer had pulled updates to A and C, but
not B. A built and installed a new version, hiding B (which was based
on an old version). The developer the build C. Cabal started with
everything hidden, then revealed A and B as specified by C's cabal
file, and the predictable build failures resulted. I have not tried
this with GHC/Cabal builds since 6.4.2, so this is probably no longer
On Nov 20, 2007 2:18 PM, Greg Fitzgerald <garious at gmail.com> wrote:
> Using GHC 6.8.1 on Windows XP, after having used ghc-pkg to expose
> 'directory-22.214.171.124', I am getting an error when I build haddock that says
> the package is hidden. When I type "ghc-pkg list", the package is not in
> parenthesis. Typing "ghc -v" says that it is using the file from
> "C:\ghc\ghc- 6.8.1\package.conf". That package.conf file has the 'exposed'
> set to True for that file. Why does GHC still think the package is hidden?
> ...\haddock-0.8>runhaskell Setup.lhs configure
> Configuring haddock-0.8...
> ...\haddock-0.8>runhaskell Setup.lhs build
> Preprocessing executables for haddock-0.8...
> shift/reduce conflicts: 5
> Building haddock-0.8...
> Could not find module `System.Directory':
> it is a member of package directory-126.96.36.199, which is hidden
> ...\haddock-0.8>ghc-pkg list
> Cabal-188.8.131.52, HUnit-184.108.40.206, OpenGL-220.127.116.11, QuickCheck-18.104.22.168,
> Win32-22.214.171.124, array-0.1.0.0, base-126.96.36.199, bytestring-0.9.0.1,
> cgi-3001.1.5.1, containers-0.1.0.0, directory-188.8.131.52, fgl-184.108.40.206,
> filepath-220.127.116.11, (ghc-6.8.1), haskell-src-18.104.22.168,
> haskell98-22.214.171.124 , hpc-0.5.0.0, html-126.96.36.199, mtl-188.8.131.52,
> network-184.108.40.206, old-locale-220.127.116.11, old-time-18.104.22.168,
> packedstring-0.1.0.0, parallel-22.214.171.124, parsec-126.96.36.199,
> pretty-188.8.131.52, process-184.108.40.206, random-220.127.116.11 ,
> regex-base-0.72.0.1, regex-compat-0.71.0.1, regex-posix-0.72.0.1,
> rts-1.0, stm-18.104.22.168, template-haskell-22.214.171.124, time-126.96.36.199,
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
The man who'd introduced them didn't much like either of them, though
he acted as if he did, anxious as he was to preserve good relations at
all times. One never knew, after all, now did one now did one now did
More information about the Glasgow-haskell-users