#8244: Removing the Cabal dependency -------------------------------------+------------------------------------ Reporter: nh2 | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.6.3 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Unknown/Multiple Type of failure: None/Unknown | Difficulty: Unknown Test Case: | Blocked By: Blocking: | Related Tickets: -------------------------------------+------------------------------------ Comment (by simonmar): Replying to [comment:3 simonpj]:
I would love to remove this dependency. Having it implies that GHC depends on heavy-duty Cabal functionality, but of course it doesn't at all. It means that we have to compile all 60+ modules of Cabal before even starting on GHC. It seems wrong.
So, more power to you! I have no opinions about the details -- just wanting to be encouraging.
Removing the Cabal dep is good of course, but I just wanted to reply to the above - the GHC ''build system'' will still depend on Cabal, because we really do use Cabal to help build the libraries that come with GHC (not to do the actual building, but to understand the .cabal files). So those 60+ modules that we have to build right off the bat will stick around, and we'll still need a full Cabal in the source tree. Perhaps it's possible to extract another subset of Cabal that we use in the build system, but that's clearly less important than extracting the bit that GHC itself depends on. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8244#comment:9 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler