Created attachment 319970 [details] asterisk-1.8.13.1:20120801-104238.log Build log should always be verbose, please force it until some EAPI includes a fix for this. Other versions might be affected as well.
All versions will be affected. Please provide rationale.
That is explained in the tracker. Do you need a patch for this?
All I see is a tracker bug with your personal opinion. The use of "should" in the RFC document way makes me ask for a -dev consensus, dev handbook excerpt or council decision before I invest time changing all my ebuilds. A non-invasive patch that applies to all ebuilds without a revision bump is okay to commit though.
In fact, this will take a patch tarball update. Please provide 1 patch that I will integrate on the next bump for each branch.
(In reply to comment #3) > All I see is a tracker bug with your personal opinion. The use of "should" > in the RFC document way makes me ask for a -dev consensus, dev handbook > excerpt or council decision before I invest time changing all my ebuilds. That is not entirely correct, see http://archives.gentoo.org/gentoo-dev/msg_ce7d33748936663e84a5463fbf7f4d39.xml and bug 384193 and bug 379497
obsolete by http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=1cc39de72ac5311db748341ef9183586556719d9