stack install succeeds (with warning) although no binaries were copied to the local-bin-path

[sjakobi]

~/s/stack $ stack install --profile --ghc-options "-O2"
Copying from /home/simon/src/stack/.stack-work/install/x86_64-linux/lts-5.3/7.10.3/bin/stack to /home/simon/.local/bin/stack

Copied executables to /home/simon/.local/bin:
- stack
~/s/stack $ rm .stack-work/install/x86_64-linux/lts-5.3/7.10.3/bin/stack 
~/s/stack $ stack install --profile --ghc-options "-O2"
Couldn't find executable stack in directory /home/simon/src/stack/.stack-work/install/x86_64-linux/lts-5.3/7.10.3/bin/
~/s/stack $ echo $status 
0

$ stack --version
Version 1.0.5, Git revision 57eb614df50826f38b923e1892cda904288a8ec9 (dirty) (3489 commits) x86_64 hpack-0.12.0

[mgsloan]

I think the most ideal way to resolve this would be to implement #1745

Perhaps this is too lenient, but it may make sense to not demand that all executables are present, particularly when building dependencies. It does make sense to fail with an exit code to indicate that something went wrong.

[mgsloan]

While this is a different issue, it's somewhat related to the general theme of conditions where executables don't get updated: #1846

[sjakobi]

I think the most ideal way to resolve this would be to implement #1745

Perhaps this is too lenient, but it may make sense to not demand that all executables are present, particularly when building dependencies. It does make sense to fail with an exit code to indicate that something went wrong.

Agreed!