On 11/1/05, Benno Schulenberg <[EMAIL PROTECTED]> wrote:
Today the updating of the portage cache was real quick -- something
like a minute, instead of the ten minutes it used to take during
the past month or so.  What has changed?

Was it the r2 to r3 update on glibc-2.3.5 ?  Did I emerge something
in the meantime that Portage uses if present but does not depend
upon?  (lzo?)  Or was a whole lot of data removed from the tree?

Benno
--
gentoo-user@gentoo.org mailing list

Have you ran some command that caches the portage dir to memory before updating portage cache? That normally speeds up.. but then again, maybe there were changes so that the annoying problem got fixed...

Fernando

Reply via email to