# emerge -p mm-sources module-init-tools These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-kernel/mm-sources-2.5.63-r1 [ebuild N ] sys-kernel/development-sources-2.5.63 [ebuild N ] sys-apps/module-init-tools-0.9.9 # emerge -p mjc-sources module-init-tools These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-kernel/mjc-sources-2.5.59-r1 [ebuild N ] sys-kernel/development-sources-2.5.63 [ebuild N ] sys-apps/module-init-tools-0.9.9 # emerge -p module-init-tools These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-kernel/development-sources-2.5.63 [ebuild N ] sys-apps/module-init-tools-0.9.9 # emerge -p development-sources These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-kernel/development-sources-2.5.63 maybe the devel kernels should depend on module-init-tools instead of the other way around, since all the devel kernels need module-init-tools, but it only wants the real devel sources. on a side note, module-init-tools-0.9.10 is out and 0.9.9 is no longer available from the SRC_URI. Reproducible: Always Steps to Reproduce: 1.emerge -p module-init-tools and any devel kernel beside development-sources Actual Results: wants to install developent-sources plus the kernel you specified Expected Results: install just the kernel you specified
maybe a virtual for development-sources would work?
This has been closed in the latest unmasked version.