Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED

[David Rientjes <rientjes@google.com>]

On Thu, 12 Jan 2012, Andrew Jones wrote:

> No, I'm putting EMBEDDED back to work doing the same thing it did before,
> i.e. the semantics for it are the same as they were before 6a108a14fa35.

Wrong, CONFIG_EMBEDDED actually had very loosely defined semantics prior 
ot 6a108a14fa35 (the renaming of CONFIG_EMBEDDED to CONFIG_EXPERT) which 
is why it was renamed in the first place.  Instead of being used solely 
for embedded devices, as you would suspect given its name and the reason 
it was introduced, it was hijacked to be used for any config option that 
was atypical for normal admins to disable and thus considered to be 
"expert" since it required a deeper level of understanding than enabling 
and disabling options at first glance or what is considered to be 
standard.  Those are two very different semantics.

> This is not a revert of that patch though. I'm keeping EXPERT, but
> ensuring it doesn't do everything EMBEDDED used to do. I'm ensuring it
> only does what it advertises it does, which is to give a useful configmenu
> cleanup symbol to the whole kernel.
> 

You're ignoring backwards compatibility for users who have already enabled 
CONFIG_EXPERT and have not enabled CONFIG_EMBEDDED (EXPERT does not select 
EMBEDDED, EMBEDDED selects EXPERT).  So if you're losing options that are 
currently configurable with CONFIG_EXPERT unless those users now enable 
CONFIG_EMBEDDED again, it's a non-starter.