Respecting global packages #60

MichaelXavier opened this Issue Jun 21, 2012 · 0 comments


None yet

1 participant


I've got a project that indirectly depends on template haskell. My dev environment has GHC 7.4.2 which must have template-haskell >= 2.6. My target environment has GHC 7.0.4, which must have template-haskell 2.5. When I try to compile in production, cabal-dev tries to go fetch the latest template-haskell (2.7) which fails to install on the old compiler. As far as I know I can't preprocess the cabal file with GHC version. Is there any way for cabal-dev to link against the global packages included with the compiler to prevent this mayhem, or is there an alternative that I'm not seeing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment