Use git version of Cabal to build stack / release version? #3550
Labels
Milestone
Comments
Once #3593 is merged in, I believe this bug will only strike when we're using pvp-bounds. We already have a mounting list of concerns around pvp-bounds, such as potentially being out-of-date with the new "soft bound" changes to the PVP. Given all of this, my recommendation is to add some comments to the release notes and documentation explaining that, due to issues with Cabal, pvp-bounds will likely not work, and recommend against using them. I don't believe it's wise for us to release Stack with an unofficial version of Cabal, or start copy-pasting code to work around Cabal bugs unless we absolutely have to. |
Makes sense to me, closing this |
snoyberg
added a commit
that referenced
this issue
Nov 22, 2017
snoyberg
added a commit
that referenced
this issue
Nov 22, 2017
Add warnings to docs/release notes about pvp-bounds #3550
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See these issues: #3549 haskell/cabal#4863
Released Cabal has a bug that makes it so that
showGenericPackageDescription
drops quite a few fields. Should we build stack-1.6 against a version of the Cabal library which has a fix? If we do that, should modify the warning message I added here: 9f06ccfNoted by phadej here:
The text was updated successfully, but these errors were encountered: