'cabal install' ignores --builddir when in sandbox #1474

Open
davidlazar opened this Issue Sep 5, 2013 · 2 comments

Projects

None yet

4 participants

@davidlazar
Contributor
$ cabal sandbox init
$ cabal install --builddir=foo

The generated build directory is dist instead of foo.

@23Skidoo 23Skidoo was assigned Sep 5, 2013
@23Skidoo
Member
23Skidoo commented Sep 5, 2013

Happens only with the install command. This is because we want to set the builddir to dist/dist-sandbox-$SANDBOX_DIR_HASH for add-source-dependencies (see #1281), but in installAction it actually gets set for all packages in the install plan. Maybe there's a way to fix this.

@23Skidoo 23Skidoo removed their assignment Jul 27, 2016
@ezyang ezyang modified the milestone: cabal-install 2.0 Sep 6, 2016
@ezyang
Contributor
ezyang commented Nov 26, 2016

This bug affects the test suite runner (we try to put all products in a special working directory, but sandbox dist dirs are not moved.)

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