On Tue, Apr 17, 2007 at 06:30:58PM +0200, Alan McKinnon wrote: > That's one way of doing it, but I believe it will be slower in the long > run. You have to load the page, read it, and decide is anything of > interest is new. If so, you then have to emerge --sync anyway, so why > not just do it reasonably often anyway? And if you use eix and run > eix-sync instead of emerge --sync, then you also get a nice display of > all changes to the tree as soon as the the sync is done. > > It is true that portage is a bit slow. If you are brave you can try > paludis (it's in the portage tree) as a replacement for portage - it's > claimed to be much faster. But, once again, it's relative: a large > update will still take many times as long to compile and install as > what it took portage to calculate what needs updating. > > Or are you actually saying that the unpack/build/install cycle takes > much longer than installing an rpm or a deb? That can't be helped, > that's how compilation works. Thanks very much, alan. The infomation you gave is very helpful, so I know maybe emerge --sync is one of best and reliable way to update, maybe it has some shortage, but I think that's a gentoo's way, I'm in gentoo's world :-) > > p.s. please don't top post I'm a novice, thank you, now I know the mailing list's rule.
-- [EMAIL PROTECTED] mailing list
