#14558: Unable to parse integer-gmp's Cabal file -------------------------------------+------------------------------------- Reporter: taylorfausak | Owner: hvr Type: task | Status: closed Priority: normal | Milestone: Component: Core Libraries | Version: 8.2.2 Resolution: fixed | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Changes (by hvr): * status: new => closed * resolution: => fixed Comment: Thanks for everyone's feedback on this issue. However, at this point the discussion is starting to go in circles and maybe we'll just have to agree to disagree; so I'll try to summarise what I consider ''technically'' relevant for the issue at hand and deliberately ignore the politically motivated aspects^(Those can be discussed those elsewhere as the GHC issue tracker is obviously not the right venue)^ and close this ticket: - GHC 8.2.x goes together with Cabal 2.0.x (which both have been released 5 months ago, which I hardly consider bleeding edge) - The compability story of GHC/Cabal has traditionally build upon the principle that the build tool fully supports the lib:Cabal version bundled with GHC; everything else is not an officially supported configuration. period. As such, Stack-1.5.1 does not deserve the label "supports GHC 8.2". - Similarly, it's not reasonable to expect to be able to parse `.cabal` files destined for the latest GHC release with an older lib:Cabal version than the one co-developed with that GHC release, as we cannot easily predict the future. - As pointed out, this merely affects the unstable branch, i.e. Stackage Nightlies, not the stable "Long Term Support" snapshots - The issue at hand doesn't impede Stack-1.5.1 users from conveniently upgrade via `stack --upgrade` and get Stack-1.6.1 which is the first Stack release that can honestly claim to "supports GHC 8.2" (even if it took merely 5 months to get there) - Stack-1.5.1 is a lost cause anyway modern as `.cabal` files will inevitably enter the package index - Going forward, we now have https://github.com/haskell/cabal/issues/4899 in place which will prevent this from repeating in the future. This way we don't have to hold back Hackage/GHC/Cabal's development for tooling to catch up; in fact, 3rd party tooling can catch up at their own convenience, even if it takes half a year, which is not uncommon in the OSS world. I'm aware that we may have to agree to disagree on some aspects. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14558#comment:40 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler