1 |
Please review. |
2 |
|
3 |
Title: Portage rsync hardlink support |
4 |
Author: Zac Medico <zmedico@g.o> |
5 |
Posted: 2018-07-11 |
6 |
Revision: 1 |
7 |
News-Item-Format: 2.0 |
8 |
Display-If-Installed: sys-apps/portage |
9 |
|
10 |
For users of the rsync tree, beginning with sys-apps/portage-2.3.42, |
11 |
the default behavior for sync operations will use hardlinks in order |
12 |
to ensure that a repository remains in a valid state if something |
13 |
goes wrong [1]. For example, if signature verification fails during a |
14 |
sync operation, the new hardlink behavior will preserve the previous |
15 |
state of the repository. |
16 |
|
17 |
The new behavior may conflict with configurations that restrict the |
18 |
use of hardlinks, such as overlay filesystems. Therefore, users will |
19 |
have to set "sync-allow-hardlinks = no" in repos.conf if they have |
20 |
a configuration that restricts the use of hardlinks, but this should |
21 |
not be very common: |
22 |
|
23 |
[DEFAULT] |
24 |
sync-allow-hardlinks = no |
25 |
|
26 |
[1] https://bugs.gentoo.org/660410 sys-apps/portage: use rsync |
27 |
--link-dest to implement atomic repository updates (and abort if |
28 |
signature verification fails) |
29 |
-- |
30 |
Thanks, |
31 |
Zac |