When installed via cabal-install, stack could potentially exhibit different behavior when compiled with different dependency versions. This sometimes makes it troublesome to diagnose stack issue reports, as it can take a long time to reach the eventual conclusion that a dependency is to blame.

See the most recent instance here - #2182

When run in verbose mode, stack should warn that it was built via cabal-install, and enumerate all the dependencies chosen. This way it's apparent that a difference in dependencies might be a suspect cause of the issue. We may also want a shorter warning when run without -v.

Similarly, when stack is built with stack, we should log which build configuration was used.