Exit with an error if $CABAL_SANDBOX_CONFIG does not point to extant file #2680
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.
I think this fixes #2224. I haven't done extensive manual testing, but the tests all (obviously) still pass.
Example output:
cabal: Cabal sandbox file in $CABAL_SANDBOX_CONFIG does not exist: foo
the "foo" is the content of the env variable.
I should note that the error occurs quite "aggressively", i.e. when the settings are read, and not when they are actually used -- so even things like "cabal info" will fail if the env variable is invalid. I think a more relaxed would be a lot more error-prone since it would be easy to miss cases.