... | ... | @@ -4,7 +4,14 @@ |
|
|
A GHC tree consists of [multiple repositories](repositories). The `sync-all` Perl script lets you operate over them all at once.
|
|
|
|
|
|
|
|
|
The basic interface to `sync-all` is described in comments at the top of the source file: source:sync-all.
|
|
|
The full documentation for `sync-all` is found by using the `--help` option:
|
|
|
|
|
|
```wiki
|
|
|
$ ./sync-all --help
|
|
|
```
|
|
|
|
|
|
|
|
|
(you can also find it by looking in source:sync-all)
|
|
|
|
|
|
## Pulling new patches
|
|
|
|
... | ... | @@ -23,10 +30,11 @@ The second step is required in the event that new packages or repositories have |
|
|
See [Building/Rebuilding](building/rebuilding) for how to update your build after pulling patches.
|
|
|
|
|
|
|
|
|
You can also pull patches from another tree:
|
|
|
You can also pull patches from another tree, by registering the other tree as a remote, and giving it a name (here `anotherghc`):
|
|
|
|
|
|
```wiki
|
|
|
$ ./sync-all -r /another/ghc pull
|
|
|
$ ./sync-all -r /another/ghc remote add anotherghc
|
|
|
$ ./sync-all pull anotherghc
|
|
|
```
|
|
|
|
|
|
|
... | ... | @@ -36,7 +44,8 @@ where `/another/ghc` is a path to another local GHC repository. You can specify |
|
|
The `sync-all` command is useful for finding out what patches you have relative to another repository:
|
|
|
|
|
|
```wiki
|
|
|
$ ./sync-all -r /another/ghc push --dry-run
|
|
|
$ ./sync-all fetch anotherghc
|
|
|
$ ./sync-all new anotherghc
|
|
|
```
|
|
|
|
|
|
|
... | ... | |