haste-inst doesn't work after fresh cabal install haste-compiler && haste-boot, in a sandbox, on Mac OS X

[bitemyapp]

[callen@localhost ~/code/haste]$ haste-inst install QuickCheck
Resolving dependencies...
cabal: Could not resolve dependencies:
next goal: haste-compiler (user goal)
rejecting: haste-compiler-0.2.99/installed-eaa... (package is broken)
trying: haste-compiler-0.2.99
next goal: ghc (dependency of haste-compiler-0.2.99)
Dependency tree exhaustively searched.

Note: when using a sandbox, all packages are required to have consistent
dependencies. Try reinstalling/unregistering the offending packages or
recreating the sandbox.

[callen@localhost ~/code/haste]$ hastec --version
0.2.99
[callen@localhost ~/code/haste]$ haste-inst --version
cabal-install version 1.18.0.3
using version 1.18.1.3 of the Cabal library
[callen@localhost ~/code/haste]$ cabal --version
cabal-install version 1.18.0.3
using version 1.18.1.3 of the Cabal library
[callen@localhost ~/code/haste]$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 7.6.3

[bitemyapp]

When I attempted the same in an hsenv:

[hsenv][callen@localhost ~/code/haste-env]$ .hsenv/cabal/bin/haste-inst install QuickCheck
Resolving dependencies...
In order, the following would be installed:
pretty-1.1.1.1 (new version)
primitive-0.5.2.1 (new package)
template-haskell-2.8.0.0 (reinstall) changes: containers-0.5.0.0 -> 0.5.5.1,
pretty-1.1.1.0 -> 1.1.1.1
time-1.4.2 (new version)
random-1.0.1.1 (new package)
tf-random-0.4 (new package)
QuickCheck-2.7 (new package)
cabal: The following packages are likely to be broken by the reinstalls:
ghc-7.6.3
Use --force-reinstalls if you want to install anyway.

[bitemyapp]

[hsenv][callen@localhost ~/code/haste-env]$ .hsenv/cabal/bin/haste-inst install lens
Resolving dependencies...
In order, the following would be installed:
filepath-1.3.0.1 (reinstall)
mtl-2.1.2 (new package)
exceptions-0.3.3.1 (reinstall) changes: mtl-2.1.2 added, transformers-0.3.0.0
added
nats-0.1.2 (new package)
parallel-3.2.0.4 (new package)
pretty-1.1.1.1 (new version)
primitive-0.5.2.1 (new package)
split-0.2.2 (new package)
syb-0.4.1 (new package)
tagged-0.7.1 (new package)
template-haskell-2.8.0.0 (reinstall) changes: containers-0.5.0.0 -> 0.5.5.1,
pretty-1.1.1.0 -> 1.1.1.1
reflection-1.4 (new package)
text-1.1.0.1 (new package)
hashable-1.2.1.0 (new package)
scientific-0.2.0.2 (new package)
attoparsec-0.11.2.1 (new package)
time-1.4.2 (new version)
transformers-compat-0.1.1.1 (new package)
contravariant-0.4.4 (new package)
distributive-0.4 (new package)
unordered-containers-0.2.3.3 (new package)
semigroups-0.12.2 (new package)
comonad-4.0 (new package)
semigroupoids-4.0 (new package)
bifunctors-4.1.1 (new package)
profunctors-4.0.2 (new package)
free-4.5 (new package)
utf8-string-0.3.7 -bytestring-in-base (reinstall) changes: bytestring-0.10.0.2
-> 0.10.4.0
vector-0.10.9.1 (new package)
aeson-0.7.0.2 +new-bytestring-builder (new package)
void-0.6.1 (new package)
zlib-0.5.4.1 (new package)
lens-4.1 (new package)
cabal: The following packages are likely to be broken by the reinstalls:
tar-0.4.0.1
process-1.1.0.2
haskell98-2.0.0.2
ghc-7.6.3
Cabal-1.18.1.3
Cabal-1.16.0
bin-package-db-0.0.0.0
executable-path-0.0.3
directory-1.2.0.1
hpc-0.6.0.0
Use --force-reinstalls if you want to install anyway.

[valderman]

In general, haste-inst and related tools currently don't play well with sandboxed environments, see #128 for instance. This is obviously a problem that should be fixed; in the meantime, using a non-sandboxed environment could be a (quite suboptimal) workaround.

[bitemyapp]

@valderman yipes. okay.

[erikkaplun]

@valderman does this mean until haste-inst starts supporting sandboxed environments, no project that uses Haste can use a sandbox?

[valderman]

@eallik I'm afraid that's the case, yes.