From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/3] bitbake: bitbake-layers: show-recipes: Show unique packagenames
Date: Wed, 18 Sep 2019 10:25:33 +1200 [thread overview]
Message-ID: <5382761.1ppftfcbhl@linux.fritz.box> (raw)
In-Reply-To: <1568347121-43357-2-git-send-email-ee.peng.yeoh@intel.com>
On Friday, 13 September 2019 3:58:39 PM NZST Yeoh Ee Peng wrote:
> Currently, show-recipes will show all recipes available (both
> recipes with different version and recipes provided by more
> than one layer).
>
> Example of default $ bitbake-layers show-recipes:
> core-image-rt:
> meta-intel unknown (skipped)
> meta unknown (skipped)
>
> yajl:
> meta-oe 2.1.0
> meta-oe 1.0.12
>
> Add -p argument to enable showing unique packagenames. This
> provide a focus view on unique recipes available.
In this context, these aren't package names, they are recipe names - so we need to be using that naming. Accordingly I would recommend -r/--recipe-only as the option name.
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2019-09-17 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 3:58 [PATCH 0/3] bitbake-layers show-recipes minor enhancement Yeoh Ee Peng
2019-09-13 3:58 ` [PATCH 1/3] bitbake: bitbake-layers: show-recipes: Show unique packagenames Yeoh Ee Peng
2019-09-17 22:25 ` Paul Eggleton [this message]
2019-09-13 3:58 ` [PATCH 2/3] bitbake: bitbake-layers: show-recipes: Select recipes from provided layer Yeoh Ee Peng
2019-09-13 3:58 ` [PATCH 3/3] bitbake: bitbake-layers: show-recipes: Enable remove the (skipped) tag Yeoh Ee Peng
2019-09-17 22:29 ` Paul Eggleton
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=5382761.1ppftfcbhl@linux.fritz.box \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ee.peng.yeoh@intel.com \
/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.