it'd be nice if the esync/eupdatedb had a --quiet option to silence all the spurious output
(In reply to comment #0) > it'd be nice if the esync/eupdatedb had a --quiet option to silence all the > spurious output eupdatedb has had a --quiet option since 2003. I'll see about adding something to esync. (Just so I've said it, though, I don't know why we have esync and eix-sync. Isn't it enough to put scripts in /etc/portage/postsync.d to run eupdatedb, update-eix, q --reinitialize, and whatever else you need?)
Created attachment 144549 [details, diff] esync_quiet.patch If esync -s isn't quiet enough for you this patch enables a -q/--quiet option that shuts it all-the-way up. This patch also changes 'emerge sync' to 'emerge --sync' internally and shortcuts a loop that doesn't need to keep looping.
(In reply to comment #1) > (Just so I've said it, though, I don't know why we have esync and eix-sync. > Isn't it enough to put scripts in /etc/portage/postsync.d to run eupdatedb, > update-eix, q --reinitialize, and whatever else you need?) portage does not run scripts in /etc/portage/postsync.d/. It runs /etc/portage/bin/post_sync. That portage-utils installs a script there which looks in postsync.d/ is another matter which won't help unless you want to RDEPEND on it... Also it has been too long since I looked at esearch but at least for eix-sync it runs diff-eix too which users will want to see if they use it..
Thanks Michael, released in esearch-0.7.1-r7
