Actually linux-{mod,info} eclasses check the kernel during the pkg_setup phase. It would be better if the check is moved to pkg_pretend function, so the user is warned an incorrect kernel config is present just after the emerge command is started and not later during the package build phase. To do an example: i'm the proxy mantainer of ati-drivers and currently i'm doing this: pkg_pretend() { if use modules; then linux-info_pkg_setup require_configured_kernel _check_kernel_config fi } pkg_setup() { if use modules; then MODULE_NAMES="fglrx(video:${S}/${FOLDER_PREFIX}/lib/modules/fglrx/build_mod/2.6.x)" BUILD_TARGETS="kmod_build" linux-mod_pkg_setup As you can see i call linux-info_pkg_setup ; require_configured_kernel, to do the check, but then calling linux-mod_pkg_setup i will do it again. The optimal setup would be to call a linux-mod_pkg_pretend in the pretend phase which does only the check (a linux-info_pkg_pretend is likely needed too), and a linux-mod_pkg_setup with checks stripped out. Likely the best solution is to bump linux-{mod,info} to linux-{mod,info}-2 so the actual behaviour is not broken in current ebuilds. Reproducible: Always
Could you not call check_extra_config in the ebuild pkg_pretend ?
