On Tue, Aug 12, 2008 at 03:53:33PM +0200, Rene Herman wrote:On 12-08-08 15:43, Adrian Bunk wrote:
Oh, how very, very important. s/RANDOM/!SPECIFIC/ then (and I meant "if RANDOM" ofcourse).Currently, we have a tristate that turns into a y/n bool if !MODULES. What would be real nice here is a tristate that turns into a m/n bool if !RANDOM, where allyesconfig and randconfig would pre-select RANDOM.allyesconfig is not random.
The point is just that such a tristate would be a one-stop mark for drivers/options that you want to be specifically selected for builtin use since they're not necessarily expected to boot on general PCs.
The part of what you want that is AFAIK not possible with the current kconfig is the "allyesconfig and randconfig would pre-select".
The actual dependencies on such an option could trivially be expressed the way you want it.
But I'm trying to make the kconfig dependencies more robust by making them less complex, and making them more complex for this developer-only
use case is nonsense.