is there a TODO/issues list for bitbake user manual enhancements?

is there a TODO/issues list for bitbake user manual enhancements?

[Robert P. J. Day]

  is there anywhere to track proposed changes to the bitbake user
manual? one of the things i've already noted is that the variable
glossary is somewhat incomplete. for example, at the very least, it
should include the following variables that are explicitly set in
bitbake's own bitbake.conf file:

 CVSDIR
 DEPLOY_DIR
 DEPLOY_DIR_IMAGE
 FILE_DIRNAME
 GITDIR
 IMAGE_CMD
 IMAGE_ROOTFS
 P
 S
 SVNDIR
 TARGET_ARCH
 TMPDIR
 WORKDIR

is there a list to add these to? or is most of the effort these days
being invested in the yocto version of the ref manual?

rday

-- 

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

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

Re: is there a TODO/issues list for bitbake user manual enhancements?

[Rifenbark, Scott M]

Robert,

The best way to track this stuff is to open a bug on it in Bugzilla 
(https://bugzilla.yoctoproject.org/).  Assign the bug to me and note 
these specific variables.

Thanks,
Scott

On 6/20/2014 10:26 AM, Robert P. J. Day wrote:
>    is there anywhere to track proposed changes to the bitbake user
> manual? one of the things i've already noted is that the variable
> glossary is somewhat incomplete. for example, at the very least, it
> should include the following variables that are explicitly set in
> bitbake's own bitbake.conf file:
>
>   CVSDIR
>   DEPLOY_DIR
>   DEPLOY_DIR_IMAGE
>   FILE_DIRNAME
>   GITDIR
>   IMAGE_CMD
>   IMAGE_ROOTFS
>   P
>   S
>   SVNDIR
>   TARGET_ARCH
>   TMPDIR
>   WORKDIR
>
> is there a list to add these to? or is most of the effort these days
> being invested in the yocto version of the ref manual?

I spend time in the BitBake manual as needed.  BTW - your patches to it 
have been applied.  They might not be in the BitBake repo yet but they 
are applied and in my contrib area.  And, of course, you can see them in 
the "latest" version of the manual.

>
> rday
>

Re: is there a TODO/issues list for bitbake user manual enhancements?

[Paul Eggleton]

Hi Robert,

On Friday 20 June 2014 13:26:08 Robert P. J. Day wrote:
>   is there anywhere to track proposed changes to the bitbake user
> manual? one of the things i've already noted is that the variable
> glossary is somewhat incomplete. for example, at the very least, it
> should include the following variables that are explicitly set in
> bitbake's own bitbake.conf file:
> 
>  CVSDIR
>  DEPLOY_DIR
>  DEPLOY_DIR_IMAGE
>  FILE_DIRNAME
>  GITDIR
>  IMAGE_CMD
>  IMAGE_ROOTFS
>  P
>  S
>  SVNDIR
>  TARGET_ARCH
>  TMPDIR
>  WORKDIR

This may seem logical at face value, but almost all of these variables aren't 
actually intrinsically understood by BitBake, they are just being provided 
there as an example of how to build something on top of BitBake (based on a 
very small subset of what OE looked like years ago). Thus, it wouldn't make 
sense to add these to the reference section of the BitBake manual.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre