Currently, equery dumps error messages (such as when asking for a non-existant ebuild) to stdout. This makes snippets like these fail horribly: for i in *; do grep DESCRIPTION $(equery which app-portage/$i 2>/dev/null); done In Unix tradition, error messages should go to stderr, not stdout. It shouldn't be too hard to fix equery accordingly. For apps which require errors on stdout, either 2>&1 can be used or maybe a cmd line switch could be added. The default should be stderr for error messages, though. If need be, I can try to write a patch.
Created attachment 35740 [details, diff] Equery stderr patch Simple patch to wrap error message output into extra function.
Will look at it.
Yeah, I'm currently reworking all of equery's output, thanks.
I think this is fixed properly now. Will be part of the next Gentoolkit release. Thanks!
In case there's been any doubt: my contributions are of course GPLv2, i.e. license-identical to that of equery.
