Kernel Configuration via XML?

dpinckard asks: "Recently, I read an article on the Web (may have been on /.) that the configuration of the newer kernel releases is getting very unwieldy. The section that interested me the most was that there still isn't a good application for configuring the kernel that works from release to release. I'd like to make a suggestion: create a directory in the source tree and each code maintainer put their config info there as an XML file. I foresee this as easing the requirements of rewriting the config app when major module rewrites happen or even when new modules appear. The app just reads all of the XML files and builds the menus." Is this a good idea or not? What do you think?"

Comments

What's the problem?

[Rob Kaper]

I hardly see a big problem with the current setup..

• Most novice users will never ever compile their own kernel.
• For those of us who do, make oldconfig will do fine for a simple kernel upgrade with no hardware changes. When you do have hardware changes, is make menuconfig really such a pain?

I think that the configuration might need to be re-catagorized for simplicity and accessibility, but I doubt whether XML or another technique will be magic pixie dust.