Messages in this thread | | | Date | Fri, 13 Aug 2004 10:00:40 -0700 | From | "Randy.Dunlap" <> | Subject | Re: [2.6 patch] let W1 select NET |
| |
On Fri, 13 Aug 2004 14:11:28 +0200 (CEST) Roman Zippel wrote:
| Hi, | | On Fri, 13 Aug 2004, Adrian Bunk wrote: | | > But the similar case of USB_STORAGE selecting SCSI is an example where | > select is a big user-visible improvement over depends. | | comment "USB storage requires SCSI" | depends on SCSI=n | | That's also user visible and doesn't confuse the user later, why he can't | deselect SCSI.
User-visible in xconfig (and gconfig?). Not in menuconfig, right? Maybe menuconfig's Help could also display dependency info...
| Abusing select is really the wrong answer. What is needed is an improved | user interface, which allows to search through the kconfig information or | even can match hardware information to a driver and aids the user in | selecting the required dependencies.
Nice idea. So are there places where SELECT is the right thing to do, i.e., it's required? (examples, please)
| Keeping the kconfig database clean and making kernel configuration easier | are really two separate problems and we shouldn't sacrifice the former for | the latter.
-- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |