On Mon, 2015-05-25 at 12:06 -0700, Josh Triplett wrote: > On Mon, May 25, 2015 at 08:25:35PM +0200, Paul Bolle wrote: > > On Mon, 2015-05-25 at 10:54 -0700, Josh Triplett wrote: > For clarity: "recursive dependency resolution" as in "recursive > resolution of dependencies", not "resolution of recursive dependencies".
I feel a headache coming up. > For an initial solution, I'd suggest just recursing through "select" > dependencies; if C has "select B", and B has "select A", enabling C > should enable B and A. Since you can't "select A || D", that seems > straightforward enough. You can "select A if X", but for that, just > bail out if the value of the expression X is changed by any of the > select statements. Actually, kconfig already recurses through select statements. (I haven't checked, but I'd expect it to handle the "select A if X" case correctly while doing the recursive select dance.) Thanks, Paul Bolle -- 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/
