From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Gkxte-0003nH-MZ for garchives@archives.gentoo.org; Fri, 17 Nov 2006 07:12:23 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kAH75vtc021018; Fri, 17 Nov 2006 07:05:57 GMT Received: from mail.netspace.net.au (cumulus.netspace.net.au [203.10.110.72]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kAH71Vw9009881 for ; Fri, 17 Nov 2006 07:01:32 GMT Received: from [172.16.0.52] (ppp246-231.static.internode.on.net [203.122.246.231]) by mail.netspace.net.au (Postfix) with ESMTP id AE25C680C3 for ; Fri, 17 Nov 2006 18:01:29 +1100 (EST) Subject: Re: [gentoo-user] How come my 'esearch' isn't updated when I emerge something until the next 'esync'?! From: Iain Buchanan To: gentoo-user@lists.gentoo.org In-Reply-To: <001a01c70a11$9329a410$450a0a0a@locutus> References: <001a01c70a11$9329a410$450a0a0a@locutus> Content-Type: text/plain Date: Fri, 17 Nov 2006 16:31:26 +0930 Message-Id: <1163746886.15826.39.camel@orpheus> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 5262965c-df83-48ff-b0cd-30b492a502fd X-Archives-Hash: a0abee86dc885e8ff4d8cced37779b8a 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 What color is a chameleon on a mirror? -- gentoo-user@gentoo.org mailing list