public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
Date: Fri, 17 Nov 2006 16:31:26 +0930	[thread overview]
Message-ID: <1163746886.15826.39.camel@orpheus> (raw)
In-Reply-To: <001a01c70a11$9329a410$450a0a0a@locutus>

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.

> *  www-apps/trac
>       Latest version available: 0.9.6
>       Latest version installed: [ Not Installed ]
[snip]
> 
> But I *DO* have it installed....
> 
> daevid ~ # emerge -av trac
> [ebuild   R   ] www-apps/trac-0.9.6  USE="cgi sqlite -enscript -fastcgi
> -postgres -silvercity -vhosts" 331 kB 
> 
> Then if I do an 'esync'

esync is the esearch tool to emerge --sync, and then eupdatedb
afterwards.  eupdatedb is the tool to update the esearch database I
mentioned earlier.

>  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 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.

> Why can't portage just be smart enough (and "smart" is a very generous term
> for the code neede to update this) to update whatever
> record/file/log/whatever it is that shows what I have installed?!

aahhh, the penny drops.  esearch is not "part" of portage, it's a tool
written by David Peter (?) to help you search the portage filesystem
easier.

There are other tools that don't require the database update, but I'll
leave that flame war for someone else to start ;)

> I've added this as a bug since I didn't see one in there already:
> http://bugs.gentoo.org/show_bug.cgi?id=155452

it will probably be marked wontfix or something like that.

You could make it practise to run eupdatedb everytime you run emerge
--sync, but that's up to you.

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

What color is a chameleon on a mirror?

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-11-17  7:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17  6:27 [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?! Daevid Vincent
2006-11-17  7:01 ` Iain Buchanan [this message]
2006-11-17 15:35   ` Bo Ørsted Andresen
2006-11-17 16:33     ` Neil Bothwick
2006-11-18 10:41     ` Robert Cernansky
2006-11-18 19:16       ` Richard Fish
2006-11-17  7:01 ` Pawel Kraszewski
2006-11-17 13:33 ` [gentoo-user] " James
2006-11-18  0:42 ` [gentoo-user] " Boyd Stephen Smith Jr.
     [not found] <7i5oL-sa-7@gated-at.bofh.it>
2006-11-17  6:52 ` Zack Elan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1163746886.15826.39.camel@orpheus \
    --to=iaindb@netspace.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox