Re: package mounting

On Tuesday 28 June 2005 11:30, Simon Marlow wrote:

So our story for portability is that code which is intended to compile on more than one system must travel with its dependencies, where those dependencies include which packages (and versions) the code requires and which compiler options are required to compile it. All this information is stored in the .cabal file, so code is portable if it is a Cabal package. Grafting locations fit into this scheme nicely.

Yes. Nevertheless, I agree with Frederik that the package should only provide a default location in the module name space. I want to be able to override this default with a compiler flag, and possibly also in the .cabal file for the client application. Ben