Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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 esearch's compact output more than eix's. It shows if you can/need update the package and if it is masked. For example, here 'U' shows that I have installed older version of screen so I should update it. And 'M' in next line shows that screenie is masked. (Descriptions are cut.) $ esearch -cF app-misc/screen [ U] app-misc/screen (4.0.3): Screen is a full-screen ... [MN] app-misc/screenie (1.30.0): Screenie is a small and ... 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 ... Found 2 matches. Robert -- Robert Cernansky E-mail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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] app-misc/screenie ((~)1.30.0): ... So it shows the version and that it is keyword masked. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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 features but eix now has far more. I especially like the ability to search all layman overlays. -- Neil Bothwick Snacktrek, n.: The peculiar habit, when searching for a snack, of constantly returning to the refrigerator in hopes that something new will have materialized. signature.asc Description: PGP signature
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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* have it installed Why can't portage just be smart enough to update whatever record/file/log/whatever it is that shows what I have installed?! esearch is separate from portage, portage DOES update it's records (that's why emerge, part of portage, shows it as installed). esearch uses a separate database (for speed) that is updated by either by esync (which also does an emerge --sync) or eudatedb. (Sorry if this has already been mentioned; I'm not receiving all the emails from the list.) -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgpA5LJCSNQUA.pgp Description: PGP signature
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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. 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
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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 you update portage with eix-sync (instead of emerge --sync) and it shows you a very detailed report of what has been updated (or downgraded) and which of these updates apply to your system. -- Pawel Kraszewski www.kraszewscy.net -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?!
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
