On Friday 17 November 2006 08:01, Iain Buchanan wrote: > On Thu, 2006-11-16 at 22:27 -0800, Daevid Vincent wrote: > > I always found this annoying... > > > > How come when I emerge something, my 'esearch' isn't updated until the > > next time I do an 'esync'? > > because esearch trawls through /usr/portage only when you tell it to, > and stores it's info in a database somewhere.
As you may know installed packages aren't stored in /usr/portage. They are installed in the vdb (/var/db/pkg). Apparently esearch doesn't look there either. As an extra bonus eupdatedb (which does look go through the vdb too) is a *lot* slower that its eix equivalent (update-eix). ;) So can anyone mention any advantage of esearch compared to eix? [SNIP] > > Then if I do an 'esync' [SNIP] > you shouldn't have to re-emerge it. portage knows about the most recent > version all the time, regardless of what esearch shows you. > > > * www-apps/trac > > Latest version available: 0.10.1 > > Latest version installed: 0.9.6 > > [snip] > > this doesn't mean that you will have to re-install. (someone can > correct me here, but) I think this means that 0.10.1 is available, but > not installed on your system probably because of masking. He said he ran `esync` rather than `eupdatedb` so yes it does seem to mean that a new version of trac has been stabilized since the last time he ran `esync`. PS: And oh.. I do agree with the rest of what you said Iain. :) -- Bo Andresen
pgpofclsXCtw6.pgp
Description: PGP signature
