On Fri, 2008-07-11 at 01:26 +0000, David Roundy wrote:
> David Roundy <droundy@darcs.net> added the comment:
> 
> On Fri, Jul 11, 2008 at 01:03:39AM -0000, David Roundy wrote:
> > So (summarizing to make sure I understand you) the conclusion is that
> > to restore sane behavior, we can just add "-hide-all-packages -package
> > base" to all our invocations of ghc? From what you describe, that's
> > what I always believed it did.  Might this be a change in behavior? It
> > seems downright ridiculous! (A quick test confirms what you describe,
> > that when compiling ghc 6.6 looks at modules that aren't explicitly
> > specified.)

Right, exactly.

> I've written a patch to make this change, but it's probably going to
> break the ghc 6.8 build.  Is there someone who will fix that if I
> push? i.e. by adding more calls like
> 
> dnl Look for Network.URI
> 
> GHC_CHECK_MODULE(Network.URI, network, undefined,,
>                  AC_MSG_ERROR(Cannot find Network.URI; try installing the package network?))
> 
> ?
> 
> If noone wants to deal with the breakage, then I'm not going to break
> new.  Otherwise, Duncan, you can always configure the set of packages
> manually by specifying
> 
> GHCFLAGS="-hide-package mtl-foo" ./configure
> 
> or whatever.

Oh sure, the workaround for me is not a problem (I just unregister
mtl-tf). It's not a blocker for me I was just reporting to help you
improve darcs.

Duncan