All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: [RFC] Identifying image recipes
Date: Thu, 02 Apr 2015 15:27:29 +0100	[thread overview]
Message-ID: <1427984849.14020.392.camel@linuxfoundation.org> (raw)
In-Reply-To: <D142FDD7.589CF%belen.barros.pena@intel.com>

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



      parent reply	other threads:[~2015-04-02 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 13:08 [RFC] Identifying image recipes Barros Pena, Belen
2015-04-02 14:17 ` Christopher Larson
2015-04-07  9:12   ` Barros Pena, Belen
2015-04-07 12:46     ` Damian, Alexandru
2015-04-02 14:27 ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1427984849.14020.392.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=belen.barros.pena@intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.