Bug 5315 - Add documentation about what each generic task does in Yocto
Summary: Add documentation about what each generic task does in Yocto
Status: VERIFIED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.6
Assignee: Scott Rifenbark
QA Contact:
URL:
Whiteboard: 31 October 2013: RESOLVED
Depends on:
Blocks:
 
Reported: 2013-10-04 09:03 UTC by Stoicescu Cornel
Modified: 2013-11-01 08:53 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2013-10-04 09:03:42 UTC 
We should have detailed documentation about what each generic task does in Yocto. These tasks do not include tasks especially designed for certain packages.

Having this documentation would make it easier for Yocto users to debug certain failures and better understand the build process.
Comment 1 Paul Eggleton 2013-10-04 12:57:18 UTC 
This should mostly be covered by the newly added "A Closer Look at the Yocto Project Development Environment" section of the reference manual; at least it does mention the task names in each section covering the related conceptual step of the build process.
Comment 2 Scott Rifenbark 2013-10-04 13:30:54 UTC 
I agree.  I think that new chapter in the reference manual covers this information.  

Look at http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#closer-look and see if this is adequate to cover this bug.  BTW - this section will continue to evolve.

Scott
Comment 3 Scott Rifenbark 2013-10-31 18:05:50 UTC 
I am marking this RESOLVED since there has been no feedback against it.
Comment 4 Stoicescu Cornel 2013-11-01 08:53:52 UTC 
The 'Bitbake' subsection from the 'A closer look' section does cover my request. Marking it as VERIFIED.