Is there any special reason why kernel-2.eclass (or any eclass) uses einfo instead of elog for post-install messages?
I was about to make a patch as a proposal, but I do need advice on the way to proceed. Should I adjust K_EXTRAEINFO to use elog, or should I make a K_EXTRAELOG and attache patches agains *-sources that uses K_EXTRAEINFO where they should use K_EXTRAELOG?
Created attachment 144712 [details, diff] convert eclass and ebuilds to using elog, add K_EXTRAELOG I left out rsbac-sources because it isn't under the kernel herd at all but it really should be converted too. I also only added the latest ebuild under each package since it's exactly the same for every version and including all of it just increases the noise. Using einfo for any of this makes it drown in the noise from epatch, running autofoo, enabling foo, etc. which all use einfo.. I'm willing to commit as much of this to as many ebuilds as I get permission for if you want...
Looks great, please commit!! Thanks a lot for working on this.
CC'ing kang so he can decide if he want to use K_EXTRAELOG in rsbac-sources too. Marking FIXED as the patch has been committed.
