1 |
On Mon, Jan 25, 2016 at 04:55:30PM +0000, Robin H. Johnson wrote: |
2 |
> On Mon, Jan 25, 2016 at 11:30:54AM +0100, Nils Holland wrote: |
3 |
> > On Sat, Jan 16, 2016 at 07:08:28AM +0000, Robin H. Johnson wrote: |
4 |
> > |
5 |
> > > All Portage calls will be including --checksum in future as well. |
6 |
> > |
7 |
> > Hmm, wouldn't this require that all "end-user facing" mirrors do |
8 |
> > actually support checksums as well? My own tiny little community |
9 |
> > mirror does, but I noticed the following: |
10 |
> Hmm, so they use 'refuse options = checksum compress'. |
11 |
> That is problematic, and we'll have to get mirrors to turn it off for |
12 |
> the gentoo-portage module. |
13 |
|
14 |
I am using that on my mirror and I have seen many other mirrors who are |
15 |
refusing it also. I would have no problem enabling compress, but as most |
16 |
mirrored data is already compressed it does not really make sense. But |
17 |
to allow checksumming is something I would rather not do. If I |
18 |
understand it correctly a rsync run, without transferring any data, |
19 |
requires all of a sudden to read 1GB of actual data from the disk |
20 |
instead of only the metadata. This is exactly the situation I am trying |
21 |
to avoid. |
22 |
|
23 |
I also see that 'refuse options' can be specified per rsync module, but |
24 |
I cannot see a way to enable it for a single module and having it |
25 |
disabled for all other modules. |
26 |
|
27 |
So, from my point of view, this new requirement sounds undesirable. |
28 |
|
29 |
Adrian |