>
> Something in the configure scripts definitely needs fixing, unless this
> feature of dep_bool and dep_tristate is intentionally not supported.
> (in which case I will revert my patch and correct the docs)
>
> One more thing, does dep_tristate work but dep_bool fails?
Both work. However, dep_bool works in different way you expected.
Michael's intention was to introduce "typed" config variables of
two separate types:
bool (with "y"/"n" as legal values)
tristate ("y"/"m"/"n" legal)
and not to mix them to simplify parsing in the future.
In effect any correct dependency for dep_bool should also be "bool".
"m" is incorrect value for bool. So "m" as a dependency for dep_bool
is treated like incorrect value -> defaulting to "n".
It may be changed, IMO (-> defaulting any incorrect value to "y"), but
such a change should be started as modification of documentation and parsers,
not config files...
The other solution is to have two separate dep_bool* function defaulting
incorrent values to different correct values (->"y", ->"n"). (IMHO worse)
Regards
Andrzej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Feb 07 2000 - 21:00:05 EST