Hi, On Fri, Feb 25, 2011 at 1:07 AM, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > We already have something remotely similar in kconfig. > We use the following list: > config DEFCONFIG_LIST > string > depends on !UML > option defconfig_list > default "/lib/modules/$UNAME_RELEASE/.config" > default "/etc/kernel-config" > default "/boot/config-$UNAME_RELEASE" > default "$ARCH_DEFCONFIG" > default "arch/$ARCH/defconfig" > I may argue that anything within the Linux tree which point _by_default_ to something outside the tree itself is broken. Say I try to build a Linux kernel on a system with has its own non-kconfig `/etc/kernel-config', I guess this would make the configuration fail. > It would be better to teach kconfig to read /proc/config.gz > and then add it to the list above. > Why ? Thing should be kept simple. kconfig's job is not to know about the trillion file format which exist in the world, even more if the implementation is made by building a command[0], executing it in a separate process and reading the output. This is the shell's job. What may be useful in the contrary would be to eventually teach kconfig to read from <stdin>. - Arnaud [0]: which is built depending on an extension, which is even more awful ... > This list is used if you just type "make enuconfig" without > any configuration. > > Sam > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
