| Summary: |
Show all layer revisions supported by Toaster, not just the ones compatible with the project |
| Product: |
[Build System, Metadata & Runtime] Toaster
|
Reporter: |
Belen Barros Pena <belen.barros.pena> |
| Component: |
toaster | Assignee: |
David Reyna <david.reyna> |
| Status: |
ACCEPTED
---
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
belen.barros.pena, brian.avery, david.reyna, jessica.zhang, jose.perez.carranza, joshuagloe, michael.g.wood, stanciux.mihail, sujith.h
|
| Version: |
2.3 | |
|
| Target Milestone: |
5.99 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
GUI design pending |
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
| Attachments: |
|
Created attachment 3281 [details] High level design - Showing all layer revisions I have received complaints about the fact that Toaster only shows you layers with branches that are compatible with the selected project release. For example, if you create a Toaster project and you choose the "krogoth" release, the list of layers Toaster shows you in that project will only include layers that, in the OpenEmbedded layer index, have a krogoth branch. If the layer you want to use doesn't have a krogoth branch, but it has a master branch, you will not find the layer anywhere in your krogoth project, and you might assume it doesn't exist. This is an issue, since users do not realise that they can import the layers to work around the release constraint. The problem could be solved by adding an option to show all layer versions supported by Toaster (normally master, plus one or two stable releases).