as to allow easy search for the recipes that generate images, this bugs tracks two items: a). adding a field in the database that points to a recipe being an image or not b). populating this field with data coming from a bitbake build; that means that bitbake, during recipe dump, tracks whenever an recipe inherits the image.bbclass magic class, and reports this in the recipe information; and Toaster build logger record this in the database; similar information must come from the LayerIndex-type layer sources.
On top of fixing one of the severe usability issues uncovered during user testing, the image recipe customisation functionality depends on Toaster being able to tell the difference between image recipes and all other recipes. Moving to 1.9, aiming for M1.
Created attachment 2507 [details] Design - Separate image recipes from all other recipes
This feature has no assignee, but the image customisation feature, as designed, relied on the ability to identify recipes that generate images.
I was asked to track the GUI work with a different entry, so I've opened bug 8039
Patch has been sent for review: https://lists.yoctoproject.org/pipermail/toaster/2015-July/002382.html
Accepted by upstream: http://cgit.openembedded.org/bitbake/commit/?id=3ac0ba73790b8f68567daa2de313c78053411fbb Removed dependency to bug 7575 as this implementation was tested with layer index from layers.pythonanywhere.com
Verified on master.