On Thursday 08 September 2005 03:18, Nick Rout wrote: > On Wed, 7 Sep 2005 09:56:24 -0500 > > Preston Hagar wrote: > > On 9/6/05, Nick Rout <[EMAIL PROTECTED]> wrote: > > > as someone already said emerge eix > > > > > > then run > > > > > > update-eix (you need to be root to do that part) > > > > > > this creates some sort of very quick index to your ebuilds which is > > > MUCH faster to search than emerge -s. > > > > > > then just use > > > > > > eix searchterm > > > ... > > > -- > > > Nick Rout <[EMAIL PROTECTED]> > > > > Another good script/program to try is esearch. Just "emerge esearch" then > > do "eupdatedb" to update the index of ebuilds. Then, the next time you do > > an "emerge sync", you can just type "esync" instead and it will update > > portage and your esearch database. It also prints out all of the updated > > packages in a nice fashion after the sync. With esearch, you can type > > "esearch searchterm" to search for packages. From my understanding (I > > have never really looked into it), it is basically locate that only > > searches through portage. It is one of my favorite gentoo tools and I > > would highly recommend it. > > > > Preston > > Yes esearch has its advantages (esync being very handy), but update-eix > seems so much faster than eupdatedb that i abandoned esearch. >
when using 'esync' why should anybody use eupdatedb? And since I do not watch the esync running but doing stuff I do not care about the minute it takes longer - but I really like the fact that esync shows all the new/updated ebuilds that were transfered. A lot of software I only saw listed there and never thought about was tried and kept after an esync ;) -- gentoo-user@gentoo.org mailing list
