Would be nice to get it at the same level of keywording as genkernel but, at least, arches with systemd keyworded should also keyword this
(In reply to Pacho Ramos from comment #0) > Would be nice to get it at the same level of keywording as genkernel Why?
Well, genkernel doesn't look to be too actively maintained, genkernel-next includes more changes and fixes apart of being more systemd friendly but, if you don't want to keyword it on hppa, it's up to you of course
HPPA uses sys-kernel/genkernel only in catalyst builds, where it more or less works because genkernel is executed in very specific ways. Its use is otherwise generally discouraged[1] for building kernels, and "manual configuration" is considered the default. sys-kernel/genkernel-next has all the HPPA specific configuration and ececution problems of sys-kernel/genkernel and isn't used anywhere right now in production. Nobody on the team seems willing to fix the genkernel default configuration problems (which would likely fix the same problems for *-next) so I don't see us supporting *-next any time soon. [1] http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml?part=1&chap=7#doc_chap2
+ 18 Jan 2014; Pacho Ramos <pacho@gentoo.org> genkernel-next-35.ebuild, + genkernel-next-50.ebuild: + ia64 keyword, bug #488046 (thanks to Emeric Maschino for testing) +
Will be done in the stabilization bug.
