| Summary: | Document automatic layer priority calculation | ||
|---|---|---|---|
| Product: | [Documentation] BitBake User Manual | Reporter: | Paul Eggleton <bluelightning> |
| Component: | bitbake-manual | Assignee: | Antonin Godard <antonin.godard> |
| Status: | ACCEPTED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | mshah, richard.purdie, srifenbark |
| Version: | unspecified | ||
| Target Milestone: | 6.2 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Paul Eggleton
2016-06-10 01:44:02 UTC
Right now we have existing descriptions for BBFILE_PRIORITY, LAYERDEPENDS, and LAYERVERSION. Is the documentation component for this bug just making sure we are saying BBFILE_PRIORITY is set now to some default if it is not explicitly set in the layer.conf file? Or, is there more to it? Scott We need to describe what happens when BBFILE_PRIORITY isn't set - i.e. the logic that figures out what the priority should be under those circumstances. I'll need to describe that of course. Given its not being used heavily do we need that automatic layer priority code? Well we just had one user tell us that they rely completely upon it. I don't think we can know how widely used it is at this point. Hi @Paul Eggleton @Richard Purdie, Is this still required? If Yes, then please provide the raw material, so that I can try to put it in the documentation. Thanks. Should we remove code instead? Bulk move from 4.99 or 0.00 to 5.99 Not sure if we should document or attempt to remove the automatic priority logic but assign to Antonin as a docs bug |