Changes between Version 29 and Version 30 of Repositories


Ignore:
Timestamp:
May 17, 2012 10:08:55 PM (2 years ago)
Author:
pcapriotti
Comment:

mention push urls for validated repositories, change darcs example from Cabal to bytestring

Legend:

Unmodified
Added
Removed
Modified
  • Repositories

    v29 v30  
    4040If the master (upstream) repo is in Git (eg `containers`), you can use the following workflow: 
    4141 1. Push the change to the upstream repo `//github.com/haskell/containers.git` 
    42  2. Push the change to the validated GHC repo for `containers`, namely [http://darcs.haskell.org/packages/containers.git] 
     42 2. Push the change to the validated GHC repo for `containers`, namely `darcs.haskell.org:/srv/darcs/packages/containers.git`. 
    4343 
    4444In other words, you don't need to interact with the git mirror on `darcs.haskell.org`. It is ''only'' there so that in step (2), the push script can check that the patch you are pushing is in the mirror, thereby ensuring that we always lag the master repo.  (For some reason this is hard to do directly on the master.) 
     
    4646Note step 2 will fail until the mirror has been updated. 
    4747 
    48 == When the master repo is in Darcs ==  
     48== When the master repo is in Darcs == 
    4949 
    50 Things are a bit more complicated when the master repo is in Darcs.  For example, to make a change to Cabal: 
     50Things are a bit more complicated when the master repo is in Darcs.  For example, to make a change to bytestring: 
    5151 
    52  1. First push the change as a darcs patch to the upstream Cabal repository, http://code.haskell.org/Cabal/ 
    53  2. The patch will be mirrored and converted to git by the mirror script, in the repo http://darcs.haskell.org/git-mirrors/Cabal/.git/ 
    54  3. You then need to pull from http://darcs.haskell.org/git-mirrors/Cabal/.git/ into `libraries/Cabal` in a regular GHC tree, validate, and push to the GHC Cabal repo, http://darcs.haskell.org/packages/Cabal.git/ 
     52 1. First push the change as a darcs patch to the upstream bytestring repository, http://darcs.haskell.org/bytestring/ 
     53 2. The patch will be mirrored and converted to git by the mirror script, in the repo http://darcs.haskell.org/git-mirrors/bytestring/.git/ 
     54 3. You then need to pull from http://darcs.haskell.org/git-mirrors/bytestring/.git/ into `libraries/bytestring` in a regular GHC tree, validate, and push to the GHC bytestring repo, `darcs.haskell.org:/srv/darcs/packages/bytestring.git`. 
    5555 
    56 == Repository locations ==  
     56== Repository locations == 
    5757{{{ 
    5858#!html