Messages in this thread | | | Subject | Re: [PATCH] Kconfig: drop bogus default values | From | Paul Bolle <> | Date | Thu, 12 Mar 2015 13:11:47 +0100 |
| |
[Removed Yann.]
On Wed, 2015-03-11 at 13:59 +0000, Jan Beulich wrote: > Default "no" is pretty pointless for options without (visible) prompts:
Related: is there ever a situation where using "default n" or "def_bool n" makes sense (whether or not the entry has a prompt)? I think I once thought of one but I can't remember it at all, so I guess my memory is fooling me.
> They only clutter .config-s with "# CONFIG_... is not set" and thus
As far as I can see the main effect of using "default n" is that this line will be printed.
> prevent users of "make oldconfig", when the option obtains a prompt or > its prompt becomes visible, noticing that these may now be enabled.
This side effect doesn't look like a feature. I scanned the source a bit but - as usual - didn't stumble on a comment that might explain this behavior. Michal probably feels better at home in the code and might be able to offer a rationale.
Paul Bolle
| |