From help: -q Be quiet (close stdout, redirecting into logfile) But instead: laverne hanno # eix-sync -q Diffing databases (11962 - 11962 packages) (eix-version 0.9.12, portage 2.1.3.9)
*This* output is intentional. It is the reason what eix-sync is for, isn't it? Maybe the description could be a bit more precise, saying that all verbose/quiet options refer to the syncing only.
Well, if it's intentional, then I don't understand it. eix-sync is, from what I understand, a tool to do the steps "sync portage" and "update the eix-database" in one step. I don't see why a "quiet" run should produce any output. It's an obvious use-case to use eix-sync -q inside a cron and there you usually don't want any output unless there appeared an error. But maybe if you think it's intentional, add another option -Q (very quiet)?
(In reply to comment #2) > eix-sync is, from what I understand, a tool to do the steps > "sync portage" and "update the eix-database" in one step. That is not its main intention: $ eix-sync -h eix-sync [options] Call layman/emerge --sync/--metadata and/or show updates. [...] ^^^^^^^^^^^^^^^^^^^ > It's an obvious use-case to use eix-sync -q inside a cron > and there you usually don't want any output unless there appeared an error. If you use it inside cron, why would you be interested to see the updates in a *log* file? (You will either want to save these data to another file or recreate it later with eix-sync -d). So it seems that you want in such a case eix-sync -q >/dev/null (or >>$DIFF_FILE) > add another option -Q (very quiet)? I have thought about it, but isn't this overkill when you can use >/dev/null as well?
Well, I'm already doing the > /dev/null-thing, but I'd consider it a more clean solution to have a parameter for it. Anyway, if you feel it's unneccessary, just close this, it isn't a big issue.
Sorry, I was wrong: I had commented from memory without looking at the code. In fact, eix-sync -q is working as you suggested. The output you see is stderr. It is inappropriate that diff-eix gives this text on stderr. This is fixed in eix's current svn trunk (eix-0.10.0).
eix-0.10.2 is stable. Includes the fix. Closing.
