Changes between Version 30 and Version 31 of Commentary/Libraries


Ignore:
Timestamp:
May 4, 2011 10:47:47 PM (3 years ago)
Author:
dterei
Comment:

change darcs to git reference

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Libraries

    v30 v31  
    55The Boot Packages, along with the other subcomponents of the GHC build system, are listed in the file `$(TOP)/packages` in a GHC tree.  
    66 
    7 All boot packages have a Darcs repo in http://darcs.haskell.org/packages: 
     7All boot packages have a Git repo in http://darcs.haskell.org/packages: 
    88 
    99 * Having all the repos in one place makes it easy and uniform for GHC developers to get all the packages. 
     
    1111 * In a build tree, these packages each occupy a sub-directory of `$(TOP)/libraries`. 
    1212 
    13  * For INDEPENDENT packages (see "Coupling to GHC", below), the Darcs repo in http://darcs.haskell.org/packages is a '''lagging repo'''. That means 
     13 * For INDEPENDENT packages (see "Coupling to GHC", below), the Git repo in http://darcs.haskell.org/packages is a '''lagging repo'''. That means 
    1414   * Don't push to it. 
    1515   * Update it from the package's master repo at convenient intervals. 
     
    7979}}} 
    8080 
    81 Some Zero-boot packages are '''maintained by other people'''. In order to avoid GHC being exposed to day-by-day changes in these packages, we maintain a "lagging" Darcs repository for each that we occasionally sync with the master repository.  We never push patches to lagging repository; rather we push to the master (in discussion with the package maintainer), and pull the patches into the lagging repo.  The current Zero-boot packages of this kind are: 
     81Some Zero-boot packages are '''maintained by other people'''. In order to avoid GHC being exposed to day-by-day changes in these packages, we maintain a "lagging" Git repository for each that we occasionally sync with the master repository.  We never push patches to lagging repository; rather we push to the master (in discussion with the package maintainer), and pull the patches into the lagging repo.  The current Zero-boot packages of this kind are: 
    8282 
    8383 * `Cabal`: we frequently update Cabal and GHC in sync 
    8484 * `binary` (renamed to `ghc-binary` in the 6.12 branch): required by `bin-package-db`. 
    8585 
    86 Other Zero-boot packages are '''maintained by us'''.  There is just one Darcs repo for each, the master.  When we make a GHC release, we simultaneously tag and release each of these packages.  They are: 
     86Other Zero-boot packages are '''maintained by us'''.  There is just one Git repo for each, the master.  When we make a GHC release, we simultaneously tag and release each of these packages.  They are: 
    8787 * `hpc` 
    8888 * `extensible-exceptions`: this is a shim that provides an API to older versions of GHC that is compatible with what the current `base` package now exports.  So, unusually, `extensible-exceptions` is a zero-boot package, but not a boot package.