| 1 |
On 07/08/2018 02:28 AM, Toralf Förster wrote: |
| 2 |
> On 07/08/2018 08:08 AM, Zac Medico wrote: |
| 3 |
>> Please review. |
| 4 |
>> |
| 5 |
>> Title: Portage rsync hardlink support |
| 6 |
>> Author: Zac Medico <zmedico@g.o> |
| 7 |
>> Posted: 2018-07-11 |
| 8 |
>> Revision: 1 |
| 9 |
>> News-Item-Format: 2.0 |
| 10 |
>> Display-If-Installed: sys-apps/portage |
| 11 |
>> IMO there's another heads-up for users having an unsual configuration: |
| 12 |
> |
| 13 |
> So we do speak about files under /usr/portage itself and not about that |
| 14 |
> dir (==changing its inode number), right? |
| 15 |
> |
| 16 |
> B/c otherwise there's another heads-up for people bind-mounting |
| 17 |
> /usr/portage onto chrooted images. |
| 18 |
|
| 19 |
This case will continue to work because the download happens in a |
| 20 |
subdirectory, and after it's verified we call rsync again to apply the |
| 21 |
changes to the top-level directory. |
| 22 |
-- |
| 23 |
Thanks, |
| 24 |
Zac |
Archives