Changes between Initial Version and Version 1 of Ticket #8244, comment 10


Ignore:
Timestamp:
Sep 12, 2013 7:28:06 PM (7 months ago)
Author:
ydewit
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8244, comment 10

    initial v1  
    33I also agree that it doesn't make sense to extract a subset of Cabal just to be used by the build system: that wouldn't add anything and possibly even make it harder to build GHC. 
    44 
    5 However, I do not follow why would the 60+ Cabal modules and the full Cabal source tree would still need to stick around. If only the GHC build system depends on Cabal for building GHC libraries, why can't Cabal be just a pre-requisite to building GHC in the same way that a recent version of GHC is a pre-requisite to building stage0? 
     5However, I do not follow why would the 60+ Cabal modules and the full Cabal source tree would still need to stick around. If only the GHC build system depends on Cabal for building GHC libraries, why can't Cabal be just a pre-requisite to building GHC in the same way that a recent version of GHC is a pre-requisite to building stage1? 
    66 
    77The way I am seeing this, once this direct dependency from GHC to Cabal is removed, GHC build system can simply state as a pre-requisite a range of Cabal versions supported. And If we do a good job extracting a minimal set of modules for this shared package that has no Cabal or GHC specific implementation details, then this shared package will rarely change and this range of supported Cabal versions will be quite wide.