[bitbake-devel] distinguishing between bitbake and "higher" layers WRT fetching variables [LONG]

[Christopher Larson]

On Fri, Jun 20, 2014 at 8:47 AM, Robert P. J. Day <rpjday at crashcourse.ca>
wrote:

>   (note: more annoying pedantry regarding bitbake configuration and
> documentation but, if i'm going to explain this to my students, i
> really need to understand it completely.)
>
>   some questions and observations about how bitbake defines some
> fetch-related variables as opposed to how those variables are defined
> in higher layers such as oe-core and poky. as richard purdie(?)
> pointed out recently, the goal should be to document bitbake as
> independently as possible from what happens in layers such as oe and
> poky, but it seems this is not as clean as it could be.
>
>   consider first bitbake's current bitbake.conf file. first, can we
> agree that this set of variables:
>

Before I dive into the remainder of the email, we should note that the
bitbake.conf in bitbake is never used when you use oe, it's solely as an
example / starting point for other non-oe projects wanting to use bitbake.
Presumably it gets forgotten about when changes to bitbake itself are made,
and so it's fallen behind.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20140620/23835e61/attachment-0002.html>