#14558: Unable to parse integer-gmp's Cabal file -------------------------------------+------------------------------------- Reporter: taylorfausak | Owner: hvr Type: task | Status: new Priority: normal | Milestone: Component: Core Libraries | Version: 8.2.2 Resolution: | 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: | -------------------------------------+------------------------------------- Comment (by dpwiz): Replying to [comment:21 Phyx-]:
Is this not a problem of stack?
Oh my... This is *exactly* the line line of reasoning that gets firebrand shaming from Linus Torvalds on LKML. I wish we were to follow it in spirit if not in, ahem, letter. No, this is not a problem of "stack" (or any other cabal-parsing tool out there). It's a problem of trust and communication. "Not my problem" is how we get into all this and still can't get out.
What I am missing here is why this is such a big deal.
Even a fringe library author should constantly ask themselves: "How many people this change would affect? Am I communicating this adequately?". And here we get major revision in core libraries.
Let's fix the tools to actually adhere to what is in the `cabal-version` fields and move on.
You can't just go and "fix" tools that are already deployed. Switching package version is a no-brainer for a hobby project, but will require major intervention at a company level. And that requires not only downloading a tarball, but examining all the changelogs and open issues. This is how Docker people are getting sneered upon in their "all right, a new version. go do the upgrade dance, everyone!". -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14558#comment:34 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler