| Summary: | Show layer dependencies recursively | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Layer Index | Reporter: | Paul Eggleton <bluelightning> |
| Component: | Layer Index | Assignee: | Piotr Buliński <piotr> |
| Status: | IN PROGRESS REVIEW --- | QA Contact: | apoorv sangal <apoorvsangal> |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | brian.avery, liezhi.yang, randy.macleod, stephano, tim.orling |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2018-03-13 02:22:56 UTC
Thinking further, I wonder if a simpler way to implement this would be to have a UI button or other action to switch the list over to the full recursive list, since it turns out that's pretty easy to get (I just added a function to do that locally for something else). bitbake-layers layerindex-fetch handles this recursive dependency checkout just fine, so it is certainly doable. One example is if meta-python is a dependency but meta-oe is not present in LAYERDEPENDS... but perhaps no recipes in the layer directly needed meta-oe. https://github.com/meta-homeassistant/meta-homeassistant/blob/fb20299f3feee001a6f91ff0d73525c00b5b40b3/conf/layer.conf#L14 From a user perspective, it might be annoying to have to declare all the recursive dependent layers in conf/layer.conf. This might be even more frustrating when trying to include dynamic-layers in LAYERRECOMMENDS, since that layer will have its own possibly recursive dependencies. The full recursive list would be nice if it was hierarchical with collapsible sub layer elements, but at least showing the hierarchy like bitbake-layers layerindex-fetch does would be a vast improvement. Still valid. |