1 |
On 11/28/2012 09:05 AM, Richard Yao wrote: |
2 |
> On 11/28/2012 09:17 AM, Maxim Kammerer wrote: |
3 |
>> On Wed, Nov 28, 2012 at 3:54 PM, Richard Yao <ryao@g.o> wrote: |
4 |
>>> We could slightly simplify the handbook installation procedure if we |
5 |
>>> told people to use emerge-webrsync to fetch the initial snapshot. |
6 |
>> |
7 |
>> Using emerge-webrsync also makes the installation process more robust, |
8 |
>> since it only requires HTTP access (whereas many firewalls restrict |
9 |
>> RSYNC). Besides, emerge-webrsync can check PGP signatures, so I think |
10 |
>> that it should be the primary recommended portage tree synchronization |
11 |
>> method. |
12 |
>> |
13 |
> |
14 |
> The only downside of which I am aware is increased network traffic. |
15 |
> However, we could redesign emerge-webrsync to take advantage of GNU |
16 |
> Tar's incremental archive functionality. |
17 |
> |
18 |
> That would permit us to mirror compressed diffs in addition to regular |
19 |
> portage snapshots. Doing that well could reduce bandwidth requirements. |
20 |
> |
21 |
weekly fulls and daily diffs? |
22 |
|
23 |
-- |
24 |
-- Matthew Thode (prometheanfire) |