On Tue, August 4, 2009 16:35, fe...@crowfix.com wrote: > On Tue, Aug 04, 2009 at 08:52:37AM +0000, Jacob Todd wrote: > > >> It sounds like you're thinking of the eix-diff application that comes >> with eix. When using eix-sync, it's run after the sync is complete to >> update the eix database; but it can be run by itself. To update a eix >> database, run 'eix-diff /var/cache/eix.previous /var/cache/eix' after >> you run eix-update. It will show all new ebuilds, what was removed, et >> cetera. > > Might do. I ran both, but eix-diff says > > > void load_db(const char*, DBHeader*, PackageTree*, PortageSettings*): > Can't open the database file '/var/cache/eix.previous' for reading (mode > = 'rb') > > > which I take as a particularly lazy way of telling me the cache hasn't > been created or is elsewhere. I'll investigate in a bit -- a quick --help > from both programs doesn't show anything obvious. Probably something > easy.
update-eix You might want to create a cron job, I have no idea if the package installs one by default. However, if you run eix-sync instead of emerge --sync, it should update the eix database as well, so running eix-update would be redundant. It will also list the diff when the sync is done if you run it manually. -- Jesús Guerrero
