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

Have verbose stack log indicate that it was built via cabal-install, and if so, which dependencies were used #2222

Closed
mgsloan opened this Issue Jun 1, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@mgsloan
Collaborator

mgsloan commented Jun 1, 2016

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.

@borsboom

This comment has been minimized.

Contributor

borsboom commented Jul 20, 2016

In conjunction with #1238, we could also log whether they're using an official binary.

@Blaisorblade

This comment has been minimized.

Collaborator

Blaisorblade commented Aug 7, 2016

Closing. I'd say this was fixed by #2222 (except for #2450) and that

In conjunction with #1238, we could also log whether they're using an official binary.

is (now) tracked by #1238.

@Blaisorblade Blaisorblade referenced this issue Aug 7, 2016

Closed

Binary upgrade code path #1238

0 of 3 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment