On Mon, May 25, 2015 at 12:55:17PM +0200, Paul Bolle wrote: > On Fri, 2015-05-22 at 14:43 -0700, j...@joshtriplett.org wrote: > > Ideally, someone should teach Kconfig to handle recursive dependencies, > > I'm probably reading too much in this remark, but how should it handle > that other than returning an error because the configuration it's fed > makes it run in circles?
I don't mean cyclic dependencies (for which Kconfig should just report an error, ideally including the full list of symbols forming the cycle). I mean that Kconfig should do recursive dependency resolution. If B depends on A, and C depends on B, I should be able to turn on C directly and have B and A enabled. As an intermediate measure, it'd be *really* handy to be able to browse in the curses UI directly from a symbol to the symbols it depends on to quickly enable/disable them, rather than having to look at the list of dependencies of a symbol, search for that symbol, remember the path the search showed, and browse there manually. - Josh Triplett -- 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/
