1 |
In v2 there's a suggestion to use git for better efficiency than rsync, |
2 |
as requested by Michał Górny: |
3 |
|
4 |
Title: Portage rsync hardlink support |
5 |
Author: Zac Medico <zmedico@g.o> |
6 |
Posted: 2018-07-11 |
7 |
Revision: 1 |
8 |
News-Item-Format: 2.0 |
9 |
Display-If-Installed: sys-apps/portage |
10 |
|
11 |
For users of the rsync tree, beginning with sys-apps/portage-2.3.42, |
12 |
the default behavior for sync operations will use hardlinks in order |
13 |
to ensure that a repository remains in a valid state if something |
14 |
goes wrong [1]. For example, if signature verification fails during a |
15 |
sync operation, the new hardlink behavior will preserve the previous |
16 |
state of the repository. |
17 |
|
18 |
The new behavior may conflict with configurations that restrict the |
19 |
use of hardlinks, such as overlay filesystems. Therefore, users will |
20 |
have to set "sync-allow-hardlinks = no" in repos.conf if they have |
21 |
a configuration that restricts the use of hardlinks, but this should |
22 |
not be very common: |
23 |
|
24 |
[DEFAULT] |
25 |
sync-allow-hardlinks = no |
26 |
|
27 |
Note that it possible to sync more efficiently using git [2] instead |
28 |
of rsync, though git consumes an increasing amount of disk space over |
29 |
time because shallow pull is currently not supported [3]. |
30 |
|
31 |
[1] https://bugs.gentoo.org/660410 sys-apps/portage: use rsync |
32 |
--link-dest to implement atomic repository updates (and abort if |
33 |
signature verification fails) |
34 |
[2] https://wiki.gentoo.org/wiki/Portage_Security#git-mirror_repo |
35 |
[3] https://bugs.gentoo.org/552814 sync using git pull --depth=1 by |
36 |
default |
37 |
-- |
38 |
Thanks, |
39 |
Zac |