On 24 April 2011 22:27, Rogan Creswick <creswick@gmail.com> wrote:

On Sun, Apr 24, 2011 at 11:13 AM, Gracjan Polak <gracjanpolak@gmail.com> wrote:
> I have a project with a .cabal file listing package dependencies using
> the usual version constraints ==X.Y.* <Z.W or >=K.J syntax.
> Standard route cabal configure; cabal build works correctly as it is able
> to select working set of package versions.
>
> I have also a .ghci file. When I run GHCi it uses all latest installed packages
> in the system. This prevents the project from loading.
>
> I tried to use 'cabal-dev ghci', but this still selects latest global packages.

This should only arise for the base ghc packages, which are tied
closely enough to ghc that you should probably switch ghc versions if
you want to work with different versions of those core packages.

If you're installing additional packages globally, my only advice is:
Beware, there be dragons! I strongly recommend that you ghc-pkg
unregister all the non-essential packages from your global package db
because:

I'll second this; I had the same problem and just uninstalled the global package and went ahead and uninstalled them all, no problems since. All my projects are under cabal-dev so it's not a problem.