On Sun, 2006-08-20 at 14:28 -0700, Isaac Jones wrote:
This simple patch just exports all the modules even when building with makefiles, just like we do in Cabal.cabal
Hmm, I expect it ought to be the other way around, that we should always hide the internal and compat modules.
Did you really need Cabal's FilePath? How about using Neils new improved stand alone version.
Isaac: what do you think?
I'm OK with exporting the module, but I think it's best not to. That module is there so that cabal can use it internally. If everyone starts to use it, then we start to get spurious dependencies on cabal; once we remove that module, other people's code will break for no good reason. Best to just admit that you're using a non-standard module and use the standalone version.
Right. Fixed. Duncan