On 18/07/12 10:55, Tom Gundersen wrote: > Linus, > >> The point I'm slowly getting to is that I would actually love to have >> *distro* Kconfig-files, where the distribution would be able to say >> "These are the minimums I *require* to work". So we'd have a "Distro" >> submenu, where you could pick the distro(s) you use, and then pick >> which release, and we'd have something like > > As someone working on one of the smaller distributions (Arch), I think > it would be even better if rather than having "distro" entries, we'd > have "application" entries. I.e., entries for applications that have > specific kernel requirements/suggestions (udev, systemd, upstart, > bootchart, pulseaudio, networkmanager, etc). If applications have soft > requirements, they could have sub-entries explaining the benefit of > enabling each.
Also coming from a 'very small distro' position; I had this problem a few months ago... my solution was this: https://github.com/lbt/mer-kernel-check/blob/master/mer_verify_kernel_config#L127 So I'd appreciate something very much along the lines of what various low-level services need and why since that way we can share work between distros and package maintainers and offer this kind of ability to our users too. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/