From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id CA845E00949; Thu, 2 Apr 2015 07:27:47 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 8FA00E00777 for ; Thu, 2 Apr 2015 07:27:45 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t32ERfB0031966; Thu, 2 Apr 2015 15:27:41 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id BAKpZfnJ3GB4; Thu, 2 Apr 2015 15:27:41 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t32ERTOg031947 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 2 Apr 2015 15:27:40 +0100 Message-ID: <1427984849.14020.392.camel@linuxfoundation.org> From: Richard Purdie To: "Barros Pena, Belen" Date: Thu, 02 Apr 2015 15:27:29 +0100 In-Reply-To: References: X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Cc: "toaster@yoctoproject.org" Subject: Re: [RFC] Identifying image recipes X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 14:27:47 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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