On 05/03/13 07:29, Borislav Petkov wrote: > On Thu, May 02, 2013 at 10:07:03PM +0200, Borislav Petkov wrote:a >> I wonder if one can exclude options from randconfig until 'select' has >> been taught to resolve dependencies... > > So I talked to Michal on IRC about the whole deal and the fact of the > matter is, unless someone steps up and rewrites the Kconfig solver so > that selects work as expected, this option would break whenever one > of those selected option's dependencies change or said option is made > configurable. > > Which means, the next best thing would be to have a small file > somewhere, maybe in scripts/kconfig/ or so, called 'allrand.config' and > which has default settings for randconfig builds. It would have > > # CONFIG_KVM_GUEST_COMMON_OPTIONS is not set > > so that this option is always disabled in randconfigs. > > Frankly, I much rather prefer this than going nuts and including every > possible dependency just so some obscure randconfigs don't break (that's > not the point of this option anyway); and then having to run around and > fix it once some of the selected option's dependencies change. > > Opinions? Could you alternately have a kvm_guest.config that should always work for you? -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|