GHC.Paths

[Claus Reinke]

> There's another problem though, which you mentioned: datadir.  The 
> datadir you used when you installed ghc-paths on your machine might not 
> be the same as the datadir used when ghc-paths was built on the target 
> machine.  So you take the binary to another machine, and the ghc-paths 
> there might be configured with a different datadir => fail.  Environment 
> variables are not a good way to fix this.

How about this (none of this is any argument against dynamic linking;-),
assuming that the executable is installed via Cabal: 

- the executable is shipped with its own data-file, which the executable 
    reads at runtime, from its own datadir
- the Setup for the executable imports the local GHC.Paths, and
    copies the info to the executable's data-file at installation time
- whichever ghc you use to install your binary is the one that will
    provide the libdir for it, via its ghc-path package

Still no cigar (not that I'd want one;-)?
Claus