From: Martin Jansa <martin.jansa@gmail.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to get a list of packages (with versions) used to create an image?
Date: Thu, 23 Jan 2014 21:26:45 +0100 [thread overview]
Message-ID: <20140123202645.GH3704@jama> (raw)
In-Reply-To: <CAFZh4h-zi=pDLr5JYgFeEfU72+qMRz2FJZ8iDt-Q3f=P+wVgKA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Thu, Jan 23, 2014 at 02:35:06PM -0500, Brian Hutchinson wrote:
> Hi,
>
> I've seen the bitbake -g command that lists the packages in an image:
>
> bitbake -g <*image>* && cat pn-depends.dot | grep -v -e '-native' | grep -v
> digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq
>
> ... but for documentation I need to generate this list with package version
> information as well.
>
> I've been just running opkg list-installed on the target but I'd like to
> know how to do this kind of thing without the target and I'm striking out
> in all the searches I've been doing.
I would recommend using buildhistory.bbclass it's really useful.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-23 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 19:35 How to get a list of packages (with versions) used to create an image? Brian Hutchinson
2014-01-23 20:26 ` Martin Jansa [this message]
[not found] ` <CAALGJZYWh+7D7C7FKxgWM+FAfhSDA9b4utGANj12bNd7t0aw6Q@mail.gmail.com>
2014-01-23 20:42 ` Brian Hutchinson
2014-01-23 21:09 ` Nicolas Dechesne
2014-01-24 11:10 ` Barros Pena, Belen
2014-01-24 13:46 ` Brian Hutchinson
2014-01-24 13:53 ` Paul Eggleton
2014-01-24 14:07 ` Brian Hutchinson
2014-01-24 14:20 ` Paul Eggleton
2014-01-24 15:05 ` Brian Hutchinson
2014-01-24 14:10 ` Barros Pena, Belen
2014-01-24 14:12 ` Barros Pena, Belen
2014-01-31 23:34 ` Trevor Woerner
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=20140123202645.GH3704@jama \
--to=martin.jansa@gmail.com \
--cc=b.hutchman@gmail.com \
--cc=yocto@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.