| 1 |
On Thu, 2006-11-16 at 22:27 -0800, Daevid Vincent wrote: |
| 2 |
> I always found this annoying... |
| 3 |
> |
| 4 |
> How come when I emerge something, my 'esearch' isn't updated until the next |
| 5 |
> time I do an 'esync'? |
| 6 |
|
| 7 |
because esearch trawls through /usr/portage only when you tell it to, |
| 8 |
and stores it's info in a database somewhere. |
| 9 |
|
| 10 |
> * www-apps/trac |
| 11 |
> Latest version available: 0.9.6 |
| 12 |
> Latest version installed: [ Not Installed ] |
| 13 |
[snip] |
| 14 |
> |
| 15 |
> But I *DO* have it installed.... |
| 16 |
> |
| 17 |
> daevid ~ # emerge -av trac |
| 18 |
> [ebuild R ] www-apps/trac-0.9.6 USE="cgi sqlite -enscript -fastcgi |
| 19 |
> -postgres -silvercity -vhosts" 331 kB |
| 20 |
> |
| 21 |
> Then if I do an 'esync' |
| 22 |
|
| 23 |
esync is the esearch tool to emerge --sync, and then eupdatedb |
| 24 |
afterwards. eupdatedb is the tool to update the esearch database I |
| 25 |
mentioned earlier. |
| 26 |
|
| 27 |
> it shows (and in some kind of ironic slap in my |
| 28 |
> face, THEN it shows me there is an update, so I have to re-emerge it to be |
| 29 |
> current): |
| 30 |
|
| 31 |
you shouldn't have to re-emerge it. portage knows about the most recent |
| 32 |
version all the time, regardless of what esearch shows you. |
| 33 |
|
| 34 |
> * www-apps/trac |
| 35 |
> Latest version available: 0.10.1 |
| 36 |
> Latest version installed: 0.9.6 |
| 37 |
[snip] |
| 38 |
|
| 39 |
this doesn't mean that you will have to re-install. (someone can |
| 40 |
correct me here, but) I think this means that 0.10.1 is available, but |
| 41 |
not installed on your system probably because of masking. |
| 42 |
|
| 43 |
> Why can't portage just be smart enough (and "smart" is a very generous term |
| 44 |
> for the code neede to update this) to update whatever |
| 45 |
> record/file/log/whatever it is that shows what I have installed?! |
| 46 |
|
| 47 |
aahhh, the penny drops. esearch is not "part" of portage, it's a tool |
| 48 |
written by David Peter (?) to help you search the portage filesystem |
| 49 |
easier. |
| 50 |
|
| 51 |
There are other tools that don't require the database update, but I'll |
| 52 |
leave that flame war for someone else to start ;) |
| 53 |
|
| 54 |
> I've added this as a bug since I didn't see one in there already: |
| 55 |
> http://bugs.gentoo.org/show_bug.cgi?id=155452 |
| 56 |
|
| 57 |
it will probably be marked wontfix or something like that. |
| 58 |
|
| 59 |
You could make it practise to run eupdatedb everytime you run emerge |
| 60 |
--sync, but that's up to you. |
| 61 |
|
| 62 |
cya, |
| 63 |
-- |
| 64 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 65 |
|
| 66 |
What color is a chameleon on a mirror? |
| 67 |
|
| 68 |
-- |
| 69 |
gentoo-user@g.o mailing list |
Archives