| 1 |
On Mon, 13 Jan 2020 12:37:11 +0100, n952162 wrote: |
| 2 |
|
| 3 |
> >>> The portage tree is sync'ed to the portage tree mirrors. A newer fs |
| 4 |
> >>> snapshot won't include the tree itself, but it will include the new |
| 5 |
> >>> default fs locations for the portage directory. |
| 6 |
> >> |
| 7 |
> >> Not sure what you mean ... you mean that the portage tree only comes |
| 8 |
> >> in with the emerge --sync? |
| 9 |
> >> |
| 10 |
> >> A preliminary copy isn't in the stage3 tarball? |
| 11 |
> > That's correct. |
| 12 |
> > |
| 13 |
> > |
| 14 |
> is this happening because I'm not using (the "optional") webrsync? |
| 15 |
|
| 16 |
It happens because the stage 3 doesn't contain a tree. The handbook tells |
| 17 |
you to run a sync after unpacking the stage 3 for that reason. webrsync |
| 18 |
is just another way of syncing, one that is more efficient than rsync |
| 19 |
when starting with an empty tree. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Neil Bothwick |
| 24 |
|
| 25 |
An expert is nothing more than an ordinary person away from home. |
Archives