i don't like the whole "What if rsync doesn't work for me?" when you download the snapshot every day and unpack it, there are phenomical things emerge does !! there are 2 ways out: 1) add that the directory should be removed every time (Attn, the distfile is too in there -> make.conf distfile overlay) or 2) portage 2.0.47+ contains emerge-webrsync, which fetches the snapshot, unpack it and rsync the portage tree with the snapshot when asking me, i prefer the 2. option more !!!
Can someone validate this as being a problem? If so, is option 2 the way to go?
I don't disagree with the remark to have emerge-webrsync as the answer (haven't tested it, but from what I gather from #gentoo it works :) but we must keep a manual way in the FAQ, since some ppl can't rsync because they just don't have any internet connection. I've tested the current FAQ-answer in a UML-environment, and this didn't break it. Martin: what is exactly wrong with this approach?
just the part with "What if rsync doesn't work for me?"
You say: "there are phenomical things emerge does !!" What exactly does it do that is not correct? As I stated before, I've used the current FAQ-explanation (downloading and untarring a snapshot) without any hassle.
the old files still remain in your local portage tree, even if we delete them from official. i had this effects. it was horrible cause some packages were broken
Ah, k. Does http://cvs.gentoo.org/~swift/faq.html give you a sufficient answer to the "What if rsync doesn't work for me?" question?
emerge-webrsync does not use rsync. it uses HTTP to download the latest portage snapshot and untar it.
look great for me
maybe add an info, emerge-webrsync uses wget, so proxy support is fully supported
Committed.