Improve build reporting for cabal-install #2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now packages specified by directory or URL work with the --build-summary option.
Member
|
@dcoutts, what do you think? |
Conflicts: cabal-install/Distribution/Client/Install.hs
dcoutts
added a commit
that referenced
this pull request
Aug 13, 2014
Improve build reporting for cabal-install
Contributor
|
Ok, I added patches for the two little issues I noted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes two changes:
cabal-installcan now generate reports for dependency solver failures. This is effectively equivalent to PR Add solver failure reporting to cabal-install #2008, with the added feature that if the--build-logoption is given,cabal-installwill save the solver output as well.cabal-installnow also creates reports for all targets, regardless of whether they were specified by name or local directory or URL. This closes--build-summarydoes not create a report for local packages #1189 and may help with No build report UI for package candidates hackage-server#74.