On Thu, 13 Jan 2011, Stephen Rothwell wrote: > Hi all, > > On Wed, 12 Jan 2011 16:58:26 -0500 (EST) Len Brown <lenb@xxxxxxxxxx> wrote: > > > > Kconfig select needs to be fixed so that it is not possible to > > select something if that something's dependencies are not met. > > So, should the config step fail if such a thing is attempted, or just not > honour the "select"? > > BTW, Linus asked me to investigate the alternative of having "select" > (recursively) automatically set the dependencies if they are not already > set ... I expect that users want to interact only with select. See feature X, enable feature X, and feature X selects what is necessary to support what the user requested... user interact with "depends-on", by comparison, is torture. Users are not offered options unless the options already have all of their dependencies met. If they manually edit the config file and enable such options, make oldconfig magically throws away their choices. That drives people crazy. cheers, Len Brown, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
