Bug 12031

Summary: Fix possibly misplaced example in section "3.4.5. INHERIT Configuration Directive"
Product: [Documentation] BitBake User Manual Reporter: caio.oliveira
Component: bitbake-manualAssignee: Scott Rifenbark <srifenbark>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: bluelightning, caio.oliveira, kristi, srifenbark
Version: unspecified   
Target Milestone: 2.4 M4   
Hardware: x86   
OS: Multiple   
Whiteboard: 13 Sept 2017: RESOLVED
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Done (doc changes complete)

Description caio.oliveira 2017-09-01 16:06:38 UTC
The last paragraph about inheriting multiple classes has an example to refer to inherit directive (that goes in the recipes) and not to INHERIT variable (that is appended in the configuration).

It also probably makes sense to mention this feature (with the example) in section "3.4.2. inherit Directive".
Comment 1 Scott Rifenbark 2017-09-02 17:16:12 UTC
Hi, 

See the new text below the first note in the inherit section (http://www.yoctoproject.org/docs/2.4/bitbake-user-manual/bitbake-user-manual.html#inherit-directive).  I have put that example there for inheriting multiple classes.

See the changes in the INHERIT Configuration Directive section (http://www.yoctoproject.org/docs/2.4/bitbake-user-manual/bitbake-user-manual.html#inherit-configuration-directive).  I changed the example at the end - guessed on the syntax. 

Let me know if these changes are okay. 

Thanks, 
Scott
Comment 2 caio.oliveira 2017-09-12 21:51:29 UTC
It looks correct to me. Thanks.

About the text in INHERIT section, I have two minor suggestions:

- Double check if autotools and pkgconfig are actually good examples of classes to be used with INHERIT (globally inherited by all recipes). There might be better examples like "buildhistory" or "rm_work".

- Just say that multiple classes are separated by spaces, can even still give the example.
Comment 3 Scott Rifenbark 2017-09-13 16:37:16 UTC
Thanks, 

I updated the text with your suggestions.  I am setting the status to RESOLVED and putting the doc flag to "done."

Scott