On Thu, 2012-07-19 at 18:35 -0400, Josh Boyer wrote:
2... yeah. I don't really know if that is going to pan out, but I am ever hopeful. I'd be mostly concerned with people that are coding userspace applications using every whiz-bang kernel feature. Or not paying attention at all to the kernel after the initial file creation and the options going stale (don't follow renames, etc).
it would be determined by the distro maintainers who maintain the kernel config for that distro.
Erm... not in Steven's scheme. At least I don't think distro kernel maintainers are going to willingly crawl through every application package that might depend on a kernel feature being enabled and maintain those files across X number of packages.
Correct. If we keep the selects in the kernel proper, then it would be the kernel maintainer to make sure it works for the necessary applications. If we have a directory called /usr/share/Linux/Kconfig.d/ then the individual packages could add their needed selects. Now this wouldn't be for the average package. We don't need emacs developers adding any configs here. It's just for those packages that are already tightly coupled with the kernel (systemd, iptables, SELinux tools, etc). -- Steve -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org