From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Finding/Generating Rootfs Package List
Date: Thu, 25 Apr 2013 17:32:39 -0500 [thread overview]
Message-ID: <5179AF07.2030708@windriver.com> (raw)
In-Reply-To: <CANge7vWGtcVQE6Sv1rn1dxWR25W99eK53UdDJjBVp2zQW=nr+Q@mail.gmail.com>
You can use the license manifest to give you this information. See:
build/tmp/deploy/licenses/<image>-<machine>-<timedate>/...
There is a license.manifest and package.manifest. The license.manifest includes
package version.
--Mark
On 4/25/13 9:10 AM, Jon Szymaniak wrote:
> Hi all,
>
> I generally like to keep a little manifest file with my rootfs images,
> containing a list of installed packages and their associated versions. On
> images where I keep package data around, I usually generate this via 'opkg list'.
>
> In my current situation, I have a small read-only image where I can't afford to
> ship pkg data, and wanted to gather this info on the host side of things. I
> assume this information is tracked somewhere in the poky build directory, but
> I'm having some trouble finding it.
>
> Could someone kindly point me towards this information or the documentation
> section(s) that I may have overlooked.
>
> Thank you!
> Jon
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2013-04-25 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 14:10 Finding/Generating Rootfs Package List Jon Szymaniak
2013-04-25 14:25 ` Burton, Ross
2013-04-25 14:49 ` Gary Thomas
2013-04-25 14:52 ` Gary Thomas
2013-04-29 13:23 ` Paul Eggleton
2013-04-25 14:27 ` Martin Jansa
2013-04-25 15:24 ` Jon Szymaniak
2013-04-25 22:32 ` Mark Hatle [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=5179AF07.2030708@windriver.com \
--to=mark.hatle@windriver.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.