On Thu, 2015-04-02 at 13:08 +0000, Barros Pena, Belen wrote: > A couple of weeks ago I ran an informal round of usability testing with > the new Toaster build functionality. One of the major issues that surfaced > was how difficult it is to identify the image recipes you can build, in > between the massive list of recipes coming from the OpenEmbedded metadata > index. It is important that the image recipes are easy to spot because > those are likely to be the first point of interest for Toaster users. > > The problem, as far as my understanding goes, is that there is no way in > the OpenEmbedded metadata to tell those apart from other recipes. We could > try and filter image recipes based on the image name (they often contain > the string '-image-'), but that would not be completely accurate. > > My question is: would it be possible to introduce a variable to identify > image recipes, I don't know, something like IMAGE_RECIPE = '1' or 'yes' > (just a wild example), that could be included in recipe files to tell > image recipes apart from standard software recipes, and that we could use > in Toaster to filter the recipe list? Is it worth proposing this to > OpenEmbedded, or there is no chance we'll get something like this through?
As Chris mentions, seeing if a recipe inherits the image class would likely be the best approach. Cheers, Richard -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
