From: Ivan Sergio Borgonovo <mail@webthatworks.it>
Cc: poky@yoctoproject.org
Subject: [SOLVED]? Re: listing PACKAGES for a certain layer
Date: Thu, 15 Oct 2015 23:37:37 +0200 [thread overview]
Message-ID: <56201CA1.1010506@webthatworks.it> (raw)
In-Reply-To: <2253318.UlfHrrQpEp@peggleto-mobl.ger.corp.intel.com>
On 10/15/2015 09:28 PM, Paul Eggleton wrote:
> Hi Ivan,
> On Thursday 15 October 2015 18:27:39 Ivan Sergio Borgonovo wrote:
>> Is there a way to list packages provided by a certain layer/recipe?
> Not layer, but you can get a bunch of info out of oe-pkgdata-util after
> recipes have been built - e.g. once the connman recipe has built you can run:
Do you mean I have to compile the package?
But probably solved in a different way:
get a list of targets from
bitbake-layers show-recipes | grep -B1 '[layer]'
join them with
bitbake -e [target] | grep 'PACKAGES='
there are still some packages coming from PACKAGES_DYNAMIC=
I'm not sure if I'm missing something else.
I'm going to write some shell script that will make things easier after
I get a better understanding of PACKAGES_DYNAMIC.
This should be the equivalent of
aptitude search '?source-package([package])'
> $ oe-pkgdata-util list-pkgs -p connman
> connman-tools
> connman-tests
> connman-client
> connman-dbg
> connman-dev
> connman-doc
> connman
and this is similar (not equal) to:
apt-file find [package]
> $ oe-pkgdata-util list-pkg-files connman
> connman:
> /etc/dbus-1/system.d/connman.conf
> /etc/init.d/connman
> /usr/sbin/connmand
But debian tools relay on an index and don't need to build stuff.
thanks
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
next prev parent reply other threads:[~2015-10-15 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 16:27 listing PACKAGES for a certain layer Ivan Sergio Borgonovo
2015-10-15 19:28 ` Paul Eggleton
2015-10-15 21:37 ` Ivan Sergio Borgonovo [this message]
2015-10-15 21:42 ` [SOLVED]? " Christopher Larson
2015-10-15 21:59 ` Ivan Sergio Borgonovo
2015-10-15 22:05 ` Christopher Larson
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=56201CA1.1010506@webthatworks.it \
--to=mail@webthatworks.it \
--cc=poky@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.