| Summary: | BBFILE_PRIORITY variable definition should explain how priority ordering works | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Documentation] Reference | Reporter: | Joshua Lock - Disabled <josh> | ||||
| Component: | handbook | Assignee: | Scott Rifenbark <srifenbark> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | gary, poky.doc.watcher, poky.watcher, sgw | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 1.0 M4 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | 22 July 2011 - Verified | ||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | --- | |||||
| Attachments: |
|
||||||
|
Description
Joshua Lock - Disabled
2011-03-04 02:25:48 UTC
It would also be good to mention that this is fully overriding. For example, if you have these recipe selections: layer-A/package/recipe_1.0.bb layer-B/package/recipe_1.2.bb If layer-A is higher priority than layer-B, recipe_1.0 will be used. To me, at least, this is not intuitive. It can be even more confusing with bbappend files. I had an example like this: layer-A/package/recipe_1.0.bbappend layer-B/package/recipe_1.0.bb layer-B/package/recipe_1.2.bb Again, if layer-A is higher priority, version 1.0 was built. I'm not sure what would be the result if the layer-B version 1.0 was deprecated and removed. All in all, just confusing. I ended up keeping all my layers the same priority as the core layers I extend upon. I think you can argue for both ways but we definitely need to document that, thanks for pointing that out Gary. Created attachment 143 [details]
Attempt at updating the BBFILE_PRIORITY variables documentation
Here's an attempt at enhancing the documentation for this variable, it could probably do with a writers touch.
Sent some feedback to Josh on the wording of the fix. Once we bottom out I will update the bug with the final wording. I have updated the description of BBFILE_PRIORITY in the Poky Reference Manual. I worked with Tom Zanussi on creating the final version of the text. The change has been commited and pushed to the yocto-docs repo and when merged with the Poky repo by either Saul or RP the bug can be closed. Hey Scott, Isn't that my input rather than Tom's? I mistakenly had Tom Zanussi mentioned as the person I worked with on this text. It was actually Joshua Lock. Sorry about that. Fixes are in |