Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
davidlazar opened this issue Sep 5, 2013 · 3 comments
Closed

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

davidlazar opened this issue Sep 5, 2013 · 3 comments

Comments

@davidlazar
Copy link
Contributor

$ cabal sandbox init
$ cabal install --builddir=foo

The generated build directory is dist instead of foo.

@ghost ghost assigned 23Skidoo Sep 5, 2013
@23Skidoo
Copy link
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.

@ttuegel ttuegel modified the milestones: cabal-install-1.24, cabal-install-1.22 Apr 23, 2015
@23Skidoo 23Skidoo modified the milestones: cabal-install 1.24, cabal-install 1.26 Feb 21, 2016
@23Skidoo 23Skidoo removed their assignment Jul 27, 2016
@ezyang ezyang modified the milestone: cabal-install 2.0 Sep 6, 2016
@ezyang
Copy link
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.)

@phadej
Copy link
Collaborator

phadej commented Aug 31, 2020

sandbox functionality is removed.

@phadej phadej closed this as completed Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants