[OE-core] clarifying details about "is not set" lines in kernel config fragment files

[Robert P. J. Day]

  one more question about fragments which i'm fairly sure i know the
answer to, but will be embarrassed about if i'm wrong.

  if i want to set a kernel option in a fragment, i'm fairly certain i
need to *explicitly* set all options it depends on, correct?
otherwise, that option is left unselected.

  is there any warning in a log file that mentions that happening?

rday

p.s. oh, and i think someone mentioned this earlier ... what happens
if i explicitly set one option, then explicitly "not set" another
option that is "select"ed by that first option? who wins?

  ok, back to work ...

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================