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

stack install always states that it installed all executabbles #605

Closed
gregwebs opened this Issue Jul 16, 2015 · 2 comments

Comments

Projects
None yet
4 participants
@gregwebs
Contributor

gregwebs commented Jul 16, 2015

When I run stack install package:exe1, It appears to only build exe1 but copy over both exe1 and exe2 into the path.

stack install fancy-api:fancy-api3 --flag fancy-api:-fdev
fancy-api-0.0.1-2fc5f00bbc8c21a5b4453ada417d72b3: unregistering (components changed)
fancy-api-0.0.1: configure
Configuring fancy-api-0.0.1...
fancy-api-0.0.1: build
Preprocessing library fancy-api-0.0.1...
In-place registering fancy-api-0.0.1...
Preprocessing executable 'fancy-api3' for fancy-api-0.0.1...
Linking .stack-work/dist/x86_64-linux/Cabal-1.18.1.5/build/fancy-api3/fancy-api3 ...
fancy-api-0.0.1: install
Installing library in
/home/haskell/frontrow/backend/.stack-work/install/x86_64-linux/lts-2.3/7.8.4/lib/x86_64-linux-ghc-7.8.4/fancy-api-0.0.1
Installing executable(s) in
/home/haskell/frontrow/backend/.stack-work/install/x86_64-linux/lts-2.3/7.8.4/bin
Registering fancy-api-0.0.1...
Installation path /home/haskell/.local/bin/ not found in PATH environment variable
Copying from /home/haskell/frontrow/backend/.stack-work/install/x86_64-linux/lts-2.3/7.8.4/bin/fancy-api2 to /home/haskell/.local/bin/fancy-api2
Copying from /home/haskell/frontrow/backend/.stack-work/install/x86_64-linux/lts-2.3/7.8.4/bin/fancy-api3 to /home/haskell/.local/bin/fancy-api3

Installed executables to /home/haskell/.local/bin/:
- fancy-api3
- fancy-api2

@borsboom borsboom added this to the 0.2.0.0 milestone Jul 21, 2015

@mitchellwrosen

This comment has been minimized.

Contributor

mitchellwrosen commented Jul 30, 2015

Is the package:component syntax supposed to work for upstream packages as well as local ones? I just had a glance over the code and it appears to only work (albeit with this bug) for local packages.

@snoyberg snoyberg self-assigned this Aug 5, 2015

snoyberg added a commit that referenced this issue Aug 5, 2015

snoyberg added a commit that referenced this issue Aug 5, 2015

@snoyberg

This comment has been minimized.

Contributor

snoyberg commented Aug 5, 2015

@gregwebs Should be fixed on master.

@mitchellwrosen No, it's only supposed to work for local stuff, much like flags. I've added a warning when a component is set in a way that it won't be used (arguably, this should be an exception instead).

@snoyberg snoyberg closed this Aug 5, 2015

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