Fix #1816 - give more descriptive errors when .cabal file cannot be found - #1824
Merged
Conversation
Avoid inline strings and manual spacing - use already-declared key variables and unwords
Particularly when dealing with add-source dependencies, it is useful to know in which directory cabal can't find a .cabal file, see: haskell#1816 Errors are also improved when installing local packages, e.g. `cabal install another/directory`.
23Skidoo
added a commit
that referenced
this pull request
Apr 27, 2014
Fix #1816 - give more descriptive errors when .cabal file cannot be found
Member
|
Merged, thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 will give better errors when a .cabal file cannot be found when:
The first patch is a simple tidy-up: removing some inline, repeated strings, and manual layout formatting.