tinderbox@ms-magpie ~ $ qsearch -a | grep gcl search: qsearch_ebuild_ebuild(): (cache update pending) app-accessibility/brltty/brltty-5.2.ebuild: No such file or directory dev-lisp/gcl GNU Common Lisp dev-python/configclass A Python to class to hold configuration values search: Updating ebuild cache ... search: initialize_flat(): opening cache failed: /var/cache/edb/dep//usr/portage/.ebuild.x: Permission denied search: initialize_flat(): You should run this command as root: q -r search: Updating ebuild cache ... search: initialize_flat(): opening cache failed: /var/cache/edb/dep//usr/local/portage/.ebuild.x: Permission denied search: initialize_flat(): You should run this command as root: q -r /me wonders if for subsequent repos the warnings can be suppressed ?
wouldn't it be easier to... generate the cache?
ofc, I did it as root afterwards. I was just curious about that - but maybe not worth he effort - I dunno.
the warning is different: the first one complains about /usr/portage while the second one complains about /usr/local/portage. we could try to track & suppress the suggestion about running `q -r` from showing up multiple times, but i don't think that's terribly valuable or worth the additional code to implement.
