On Jan 16 Linus Torvalds wrote: > Or do you expect a high-quality implementation of a configuration > script to allow the user to just say "I want ocfs2", and then figure > out the dependencies and solve them for you? > > I'd say that the latter case is OBVIOUSLY the quality implementation, > while the former one is just stupid. As Al noted, there also needs to be a convenient way to *disable* options. Hence, the Kconfig files should merely declare the dependencies. Then, some user interfaces should deal with the this database of dependencies and let different people achieve different goals as easily as possible. We already have different UIs. But perhaps we have too much UI down in the Kconfig files. I.e., perhaps Kconfig shouldn't know the difference between depends-on and select. Let the different UIs present the dependency graph to the operator in different ways, suitable to different tasks. /handwave off. -- Stefan Richter -=====-==-== ---= =---= http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
