On Fri, 18 Feb 2005 14:17:09 -0600, Alvaro Zuniga <[EMAIL PROTECTED]> wrote:
> What is the greatest pain in the @(*#& when dealing with Gentoo.
For me it is maintaining ebuilds in the overlay. Followed closely by
adding keywords to /etc/portage/package.keywords for packages I want
to test and package specific useflags to /etc/portage/package.use for
flags I don't want in make.conf
> Anyway, I came across a great utility called "esearch" Those gentoo
> users that have never used it are going to be impress with the speed.
Yes, esearch rocks!
> The only drawback is that the portage tree has to be indexed everytime
> you do an "emerge sync".
Also esearch's index includes things like installed packages, and mask
status. So adding a package to a system overlay or installing
package(s) will not be seen untill eupdatedb is rerun.
> I do not do to many syncs unless absolutely
> necessary. If I cared about being up to date, I would probably have cron
> do both the index rebuild and emerge sync a week or so.
A cron for eupdatedb is included with the package
/usr/share/doc/esearch-0.7/eupdatedb.cron.gz
I have a sync cron that runs daily:
#! /bin/sh
/usr/bin/emerge sync
if [ -x /usr/sbin/eupdatedb ]
then
nice /usr/sbin/eupdatedb
fi
