From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Edward Vidal <vidal.develone@gmail.com>
Subject: Re: beagleboard, qemuarm, beaglebone, and pandaboard images.
Date: Tue, 16 Apr 2013 15:49:52 +0100 [thread overview]
Message-ID: <1702801.pL1SCMygr1@helios> (raw)
In-Reply-To: <CAJTo0LZjwYj04fw6wq6HBsT1v5UQjCKYc6he8rNudBL+B0dyng@mail.gmail.com>
On Tuesday 16 April 2013 15:03:50 Burton, Ross wrote:
> On 16 April 2013 15:01, Edward Vidal <vidal.develone@gmail.com> wrote:
> > I did a search for installed-pkgs.txt and complementary-pkgs.txt neither
> > of
> > these files were on my system. I am assuming this is because in my
> > local.conf I am using INHERIT += "rm_work".
> > as found on page 41 of the ref_manual. What is the difference between the
> > two pkgs sets? The does reduce the capabilities of the systems? Can the
> > complementary-pkgs.txt be installed with a flag?
>
> Yes, rm_work will delete those files.
>
> As far as I know, "installed" is the packages explicitly installed,
> "complementary" is the set installed through features such as
> dev-pkgs.
>
> If you really want to find the differences on these images, boot each
> and dump the installed package list (rpm -qa?).
Or, use buildhistory:
https://wiki.yoctoproject.org/wiki/Buildhistory
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-04-16 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 0:00 beagleboard, qemuarm, beaglebone, and pandaboard images Edward Vidal
2013-04-16 8:54 ` Burton, Ross
2013-04-16 14:01 ` Edward Vidal
2013-04-16 14:03 ` Burton, Ross
2013-04-16 14:35 ` Edward Vidal
2013-04-16 14:41 ` Burton, Ross
[not found] ` <CANwz6nypaO6k6qWqu+3yGB0CTY8C_ko0jurkrwtO=v4umvWvHw@mail.gmail.com>
2013-04-16 15:02 ` Burton, Ross
2013-04-16 15:09 ` Edward Vidal
2013-04-16 14:49 ` Paul Eggleton [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=1702801.pL1SCMygr1@helios \
--to=paul.eggleton@linux.intel.com \
--cc=vidal.develone@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.