On Monday 09 January 2006 04:37, Stroller wrote: > > aaahhh, the wait for eupdatedb, yes it does take a while (certainly > > not > > 90 minutes, more like 5 minutes for me) but then I run it from cron at > > lunch, so I don't notice... much :) > > I think you meant to say: > aaahhh, the wait for eupdatedb, yes it does take a while > (certainly not > 90 minutes for me, more like 5 minutes) > > I have no intention of timing it here and now, but I have one system > here on which eupdatedb is certainly into the several tens of minutes.
You know, you could all just use: http://gentoo-wiki.com/TIP_speed_up_portage_with_cdb Then get ultra fast metadata updates (no 50-51% hang*), quick searches (not as quick as eix or esearch but *way* quicker than portage standard), and no need to update a second database (so no out of date searches). carpaskis thoughts are perfectly valid, but if you know you're using cdb then get a seg fault, you can turn it off. * Under 52 seconds, with no previous portage interactions in hours, while reading email in kmail, on a 7200rpm 2.5" drive in a PM 1.8. -- Mike Williams -- gentoo-user@gentoo.org mailing list
