#8244: Removing the Cabal dependency -------------------------------------+------------------------------------- Reporter: nh2 | Owner: duncan Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.6.3 Resolution: | Keywords: Operating System: | Architecture: Unknown/Multiple Unknown/Multiple | Difficulty: Unknown Type of failure: | Blocked By: None/Unknown | Related Tickets: Test Case: | Blocking: | Differential Revisions: D172 | -------------------------------------+------------------------------------- Comment (by refold): ezyang: What I had in mind was upgrading, say, Cabal 1.22 -> 1.24 when going from GHC 7.10.2 to GHC 7.10.3. Since GHC API will no longer depend on Cabal, this should be less of a problem.
So, the only way to make Cabal separately upgradeable is by siphoning ghc-pkg off into a proper package, relaxing the tight coupling and upgrading it when you upgrade Cabal.
Is splitting the parts of Cabal ghc-pkg uses into a separate library out of the picture? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8244#comment:27 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler