bitbake variable glossary versus YP (ref manual) variable glossary?

bitbake variable glossary versus YP (ref manual) variable glossary?

[rpjday]

  was puzzled over a lack of some important BB_* variables in the ref
manual variable glossary, until i remembered the bitbake user manual,
where i can find them, but there is an inconsistency between the two
manuals in that *some* of the BB_* variables are listed in the ref
manual variable glossary (eg., BB_NUMBER_THREADS) but not others (eg.,
BB_NO_NETWORK), which could lead to some confusion.

  even weirder, some are in the ref manual while *not* in the bitbake
user manual variable glossary (eg., BB_SERVER_TIMEOUT). is there some
sort of pattern as to which variables go in which variable glossary?
as it is, it's definitely inconsistent, requiring one to bounce back
and forth for a complete coverage.

rday

-- 

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

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

Re: [docs] bitbake variable glossary versus YP (ref manual) variable glossary?

[Richard Purdie]

On Wed, 2020-03-25 at 13:45 -0400, rpjday@crashcourse.ca wrote:
>   was puzzled over a lack of some important BB_* variables in the ref
> manual variable glossary, until i remembered the bitbake user manual,
> where i can find them, but there is an inconsistency between the two
> manuals in that *some* of the BB_* variables are listed in the ref
> manual variable glossary (eg., BB_NUMBER_THREADS) but not others
> (eg.,
> BB_NO_NETWORK), which could lead to some confusion.
> 
>   even weirder, some are in the ref manual while *not* in the bitbake
> user manual variable glossary (eg., BB_SERVER_TIMEOUT). is there some
> sort of pattern as to which variables go in which variable glossary?
> as it is, it's definitely inconsistent, requiring one to bounce back
> and forth for a complete coverage.

I think this is just incorrect. The bitbake manual should define the
variables implemented in bitbake, particularly the BB* namespace.

Cheers,

Richard