All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: Re: [Webhob] Deployed or Included?
Date: Mon, 8 Jul 2013 12:13:24 -0500	[thread overview]
Message-ID: <51DAF334.3030807@windriver.com> (raw)
In-Reply-To: <CE00A2D0.2D4B9%belen.barros.pena@intel.com>

On 07/08/2013 11:09 AM, Barros Pena, Belen wrote:
> I am looking at the table of packages that will be part of Web Hob. That
> table will list all packages built during a certain build.

What table are you making a reference to?   I didn't see a pointer in the e-mail.

>
> Not all the packages in that table ended up in the final image. To
> differentiate them, there will be a column that will tell you if a package
> is in the final image or isn't. How should that column be called:
> Deployed? Included? Something else?

There is a distinct possibility that the number of packages built to support the webhob that go on the final target image is zero, particularly in the case that you just need a particular configuration of busybox + a kernel.

Without seeing your table it is hard to say, but generally we have nativesdk, native, cross and target packages.  I would have imagined you can just specify if something is in the target image or not.  There certainly are target packages that get built but not installed to the image, and for these we just use the term installed to sysroot vs installed to image.

Jason.



  reply	other threads:[~2013-07-08 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 16:09 [Webhob] Deployed or Included? Barros Pena, Belen
2013-07-08 17:13 ` Jason Wessel [this message]
2013-07-09 17:29   ` Barros Pena, Belen
2013-07-09 17:42     ` Jeff Osier-Mixon
2013-07-09 17:51       ` Barros Pena, Belen
2013-07-09 17:56         ` Jeff Osier-Mixon

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=51DAF334.3030807@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=belen.barros.pena@intel.com \
    --cc=webhob@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.