Changes between Version 7 and Version 8 of DarcsConversion


Ignore:
Timestamp:
Aug 27, 2008 3:00:18 PM (6 years ago)
Author:
simonmar
Comment:

start sketching what to do about libraries

Legend:

Unmodified
Added
Removed
Modified
  • DarcsConversion

    v7 v8  
    6060 * TestingPatches 
    6161 * BuildBot 
     62 
     63== Plan for libraries == 
     64 
     65The remaining question is what to do about the library repositories.  It is possible to work with the GHC repository in git and all the other repositories in darcs, but this can't be a long-term strategy: our motivation for moving away from darcs is invalid if parts of the repository still require darcs.  We need a strategy for a single-VCS solution. 
     66 
     67Here's a tentative plan: 
     68 
     69 * Some libraries belong to GHC (template-haskell, ghc-prim, integer-gmp, hpc), and for these we can convert 
     70   the repos to git and keep them as subrepos.  (alterantively we could just import them into the main 
     71   git repository for convenience). 
     72 
     73 * Of the rest, base is somewhat special, because this alone often needs to be modified at the same time as GHC.  We propose migrating base to a git repository. 
     74 
     75 * For the rest of libraries (e.g. filepath, containers, bytestring, editline), GHC is just a client, and we don't expect to be modifying these libraries 
     76   often.  Hence we can just copy the libraries wholesale into the GHC git repository, and update the copies 
     77   occasionally when a new version of the library is released.  We can provide a way to update the GHC copy from 
     78   the official darcs repository easily.  The local copy would be read-only, except when updating from the master copy.