In the firmware discussion on -dev mailing list, it was suggested to add a "firmware" USE-flag to virtual/linux-sources that triggers a dependency on sys-kernel/linux-firmware. Whether to enable it by default or not (or in the desktop profile) would be your call.
I didn't follow that discussion. What you're asking is pretty straight forward. Would the following suffice: --- linux-sources-0.ebuild.orig 2013-02-13 20:24:33.000000000 -0500 +++ linux-sources-0.ebuild 2013-02-13 20:25:34.000000000 -0500 @@ -11,9 +11,9 @@ LICENSE="" SLOT="0" KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86" -IUSE="" +IUSE="firmware" -DEPEND="" +DEPEND="firmware? ( sys-kernel/linux-firmware )" RDEPEND="|| ( sys-kernel/gentoo-sources sys-kernel/vanilla-sources
Yes, that would work.
(In reply to comment #2) > Yes, that would work. Okay I just noticed that sys-kernel/linux-firmware is not keyworded for all arches while virtual/linux-sources is: 1) For sys-kernel/linux-firmware we have at least one version stable on amd64, arm and x86. And we only have ~ia64. No other keyworded arches. 2) For virtual/linux-sources-0 we have KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86" So, 1) The following arches either mask or keyword sys-kernel/linux-firmware: alpha hppa mips ppc ppc64 s390 sh sparc" 2) I will add virtual/linux-sources-1 to the tree with KEYWORD="~amd64 ~arm ~ia64 ~x86" and as the arches keyword/mask sys-kernel/linux-firmware on their arches, just expand the KEYWORD list.
HPPA is up to the keywording level of the other stable arches.
Marked ~hppa.
Added ~alpha and ~mips.
Keyworded ~ppc ~ppc64.
Ping s390, sh and sparc.