| Summary: | How come my 'esearch' isn't updated when I emerge something until the next 'esync'?! | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daevid Vincent <daevid> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Sure, everytime you emerge something, we'll run the db update that takes minutes to complete and is pretty disk intensive... Feel free to use /usr/share/doc/esearch-<version>/eupdatedb.cron.gz sample cronjob and stick it to cron.hourly or run it from crontab every 5 minutes, but don't request such annoying stuff please. |
I always found this annoying... How come when I emerge something, my 'esearch' isn't updated until the next time I do an 'esync'? * www-apps/trac Latest version available: 0.9.6 Latest version installed: [ Not Installed ] Size of downloaded files: 995 kB Homepage: http://trac.edgewall.com/ Description: Trac is a minimalistic web-based project management, wiki and bug/issue tracking system. License: trac 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' it shows: * www-apps/trac Latest version available: 0.9.6 Latest version installed: 0.9.6 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?! This seems so silly and like a 0.0.3 kind of feature to put in to portage.