| 1 |
On Aug 10, 2005, at 24:42, Grobian wrote: |
| 2 |
|
| 3 |
> | Note: With each emerge --sync, the /usr/portage directory is |
| 4 |
> wiped of |
| 5 |
> | any user changes. Be sure to keep a log of your development efforts |
| 6 |
> | and report your findings to the Gentoo for Mac OS X team. |
| 7 |
> |
| 8 |
> Ehm, is this really true? I vaguely remember in my first days |
| 9 |
> doing this thinking a sync would wipe out my mess, then coming to |
| 10 |
> the conclusion it didn't. I don't know exactly how rsync is being |
| 11 |
> called, but if a file is newer on the target host, than on the |
| 12 |
> server, is it overwritten? I thought rsync is able to optimise by |
| 13 |
> only beaming over the changed files on the server side, preventing |
| 14 |
> copying all of the files (550MB currently). Somebody slap me with |
| 15 |
> the man page and the massive number of options supplied to rsync |
| 16 |
> when running emerge sync if I see ghosts here... |
| 17 |
|
| 18 |
AFAIK, yes. Any time I've made changes to /usr/portage and then did a |
| 19 |
sync, regardless of whether or not there was an actual update to that |
| 20 |
file in the meanwhile, my changes were overwritten. |
| 21 |
|
| 22 |
Feel free to attack me with a medium-sized herring if I'm completely |
| 23 |
wrong in throwing in said <note>. I just thought that note would be a |
| 24 |
nice thing to have in there for anyone who was confused at this |
| 25 |
functionality. If anyone feels as though it shouldn't be there, |
| 26 |
please let me know and I'd be glad to remove it. |
| 27 |
|
| 28 |
-- |
| 29 |
|
| 30 |
Hasan Khalil |
| 31 |
eBuild and Porting Co-Lead |
| 32 |
Gentoo for Mac OS X |
Archives