All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Jon Szymaniak <jon.szymaniak@gmail.com>
Subject: Re: Finding/Generating Rootfs Package List
Date: Mon, 29 Apr 2013 14:23:52 +0100	[thread overview]
Message-ID: <2300560.dNxvkzWty1@helios> (raw)
In-Reply-To: <CAJTo0LbzYsOdZ_We_q6VsdfgrdGU9syaRDyXJxe-eu_tAjS0Mw@mail.gmail.com>

On Thursday 25 April 2013 15:25:10 Burton, Ross wrote:
> On 25 April 2013 15:10, Jon Szymaniak <jon.szymaniak@gmail.com> wrote:
> > 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.
> 
> In tmp/work/[machine]/[image]/[version]/ you'll find
> installed-pkgs.txt and complementary-pkgs.txt, which should be exactly
> what you want.

I would advise against using installed-pkgs.txt and complementary-pkgs.txt for 
anything; the former only includes the list of packages before complementary  
and locale package installation and is internal so it might go away at some 
point if the implementation changes.

Martin already mentioned buildhistory, that's the best choice for getting this 
information (or programmatically you can use the same method it does for 
collecting the information, i.e. calling list_installed_packages from a 
function added to ROOTFS_POSTPROCESS_COMMAND, if you prefer).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2013-04-29 13:23 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 [this message]
2013-04-25 14:27 ` Martin Jansa
2013-04-25 15:24   ` Jon Szymaniak
2013-04-25 22:32 ` Mark Hatle

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=2300560.dNxvkzWty1@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=jon.szymaniak@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.