1 |
Hi there! |
2 |
|
3 |
|
4 |
My impression is that: |
5 |
|
6 |
* a large number of people still sync /usr/portage using plain rsync, |
7 |
|
8 |
* it is not a trivial choice which source to switch to. |
9 |
|
10 |
Do we have documentation comparing options for syncing /usr/portage? |
11 |
|
12 |
|
13 |
The rest of this mail is a collection of methods that I am aware of. |
14 |
It could become the start of a wiki page if missing or so. |
15 |
|
16 |
Best |
17 |
|
18 |
|
19 |
|
20 |
Sebastian |
21 |
|
22 |
|
23 |
=== |
24 |
|
25 |
Sync options that I am aware of include: |
26 |
|
27 |
* Plain rsync |
28 |
|
29 |
* Git: 4x direct source (Ebuilds + DTD + GLSA + News) |
30 |
|
31 |
* Git: combined mirror [1] |
32 |
|
33 |
* webrsync: Plain |
34 |
|
35 |
* webrsync: With GPG [2] |
36 |
|
37 |
* ..? |
38 |
|
39 |
|
40 |
The key questions for differences and picking I see are: |
41 |
|
42 |
* Does it use secure transport, e.g. SSL? |
43 |
|
44 |
* Does it verify GPG signatures? |
45 |
|
46 |
* Does it support incremental updates? |
47 |
|
48 |
* Does it come with metadata/md5-cache pre-generated? |
49 |
|
50 |
* How much delay does it have? |
51 |
|
52 |
|
53 |
[1] https://github.com/gentoo-mirror/gentoo |
54 |
[2] http://blog.siphos.be/2011/07/emerge-webrsync-and-gpg-verification/ |