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

[Robert P. J. Day]

On Tue, 3 May 2016, Denys Dmytriyenko wrote:

> On Tue, May 03, 2016 at 02:27:38PM -0400, Robert P. J. Day wrote:
> > On Tue, 3 May 2016, Bruce Ashfield wrote:
> >
> > > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> > >
> > >         oddly, in the current YP kernel dev manual, i don't see the
> > >       phrase "is not set" explained anywhere in the entire doc,
> > >       which is weird since it seems like it would be important.
> > >
> > > The manuals don't cover the mechanics of how the mainline kernel is
> > > configured. Just the same way the don't cover the configuration
> > > language for any number of packages in the system.
> >
> >   assuming i'm understanding your position, that's where i'm going to
> > *strongly* disagree. people who work with the mainline kernel in a
> > non-OE environment don't use kernel config fragment files. period.
> > AFAIK (and correct me if i'm wrong), .cfg kernel config fragment files
> > are exclusively an OE/YP thing, so there is no reason for normal
> > kernel developers to understand how they work.
>
> You are *strongly* wrong! I know many kernel developers using this:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/scripts/kconfig/merge_config.sh

  ah, i was unaware of that. ok, a short reference to that would work
just fine.

rday

-- 

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

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