On Fri, 17 Nov 2006 16:35:28 +0100 Bo Ørsted Andresen [EMAIL PROTECTED] wrote:
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?
I like
On 11/18/06, Robert Cernansky [EMAIL PROTECTED] wrote:
eix gives following output on the same request:
$ eix -cA app-misc/screen
[I] app-misc/screen (4.0.2-r5): Screen is a full-screen ...
[N] app-misc/screenie (): Screenie is a small and ...
Hmm, eix 0.8.1 on my system produces:
[N]
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
On Fri, 17 Nov 2006 16:35:28 +0100, Bo Ørsted Andresen wrote:
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?
Not any more. esearch used to win on
On Friday 17 November 2006 00:27, Daevid Vincent [EMAIL PROTECTED]
wrote about '[gentoo-user] How come my 'esearch' isn't updated when I
emerge something until the next 'esync'?!':
How come when I emerge something, my 'esearch' isn't updated until the
next time I do an 'esync'?
But I *DO*
On 2006-11-17 07:30:11 +0100
Daevid Vincent [EMAIL PROTECTED] 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.
Dnia piątek, 17 listopada 2006 07:27, Daevid Vincent napisał:
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 it is the way it is designed.
Well, it is a high time to switch from esearch to eix. Then
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
8 matches
Mail list logo
