Add cabal files to resolve build issues with stack>=2.1.* #9
Conversation
This file contains 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
Martoon-00
approved these changes
May 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
✅ Checklist for your Pull Request
It is a known fact that Stack, starting from versions 2.1.*, cannot into imported hpack configuration files for Git-fetched extra deps: commercialhaskell/stack#4906
Even better, this issue is a
wontfix, so Stack is not even expected to support this anymore in later versions.As
servant-utilis widely used throughout Serokell projects, mostly as a git-fetched extra dep, this prevents newer stack versions to be able to build lots of Serokell projects.We can resolve this just by using older versions of stack throughout the company, but frankly it is better to just include
.cabalfiles in this repo.