Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!

[Zack Elan <zackelan@gmail.com>]

On 2006-11-17 07:30:11 +0100
"Daevid Vincent" <daevid@daevid.com> wrote:

> How come when I emerge something, my 'esearch' isn't updated until
> the next time I do an 'esync'? 

Because esearch uses a database to speed up searches, and that database
isn't regenerated until you run esync or eupdatedb.

I'd recommend using eix instead of esearch - not only is it faster, but
it also knows changes in installed packages without needing to update
its database.

> Then if I do an 'esync' it shows (and in some kind of ironic slap in
> my face, THEN it shows me there is an update, so I have to re-emerge
> it to be current):

You should probably be doing eupdatedb instead of esync. esync does an
emerge --sync, and you don't want to get banned from a mirror for
rsync abuse.

> This seems so silly and like a 0.0.3 kind of feature to put in to
> portage.

It's not a part of portage. esearch is a separate package, developed
specifically to combat the slowness of emerge --search.
-- 
gentoo-user@gentoo.org mailing list