From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: Core image recipes
Date: Fri, 26 Aug 2011 09:18:15 -0700 [thread overview]
Message-ID: <4E57C747.2020104@linux.intel.com> (raw)
In-Reply-To: <201108261047.10782.paul.eggleton@linux.intel.com>
On 08/26/2011 02:47 AM, Paul Eggleton wrote:
> Hi all,
>
> Seems we have a few overlapping images in OE-core, with not especially obvious
> naming. The following two seem very similar in scope (basic X11 image):
>
> meta/recipes-core/images/core-image-core.bb
This contains X11_IMAGE_FEATURES
> meta/recipes-extended/images/core-image-basic.bb
>
This image should NOT contain any X11, this is supposed to be an
extention of core-image-minimal with many of the busybox related
commands substituted for the real command set. The intention of this
image is two fold, first it's the largest image that we test against
non-GPLv3 and it's the non-graphical LSB image (I am not sure if there
is a spec test defined for that.
> Maybe we could just have one of these and call it core-image-x11-base or
> similar?
>
So, no I do not think they can be merged. But renaming core-image-core
to core-image-x11-base might make sense, also renaming core-image-basic
to core-image-lsb-basic may clear things up.
> Then, we have core-image-base, which whilst it doesn't remove package
> management files, does not have "package-management" in its features, so it's
> not a whole lot different to core-image-minimal AFAICT.
>
On this one I might agree, I know that we have not built that image, nor
does it seem to be used by anything else.
Sau!
> Comments?
>
> Cheers,
> Paul
>
>
next prev parent reply other threads:[~2011-08-26 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 9:47 Core image recipes Paul Eggleton
2011-08-26 16:18 ` Saul Wold [this message]
2011-08-26 16:39 ` Paul Eggleton
2011-09-07 13:18 ` Paul Eggleton
2011-09-08 3:53 ` Saul Wold
2011-09-08 7:35 ` Paul Eggleton
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=4E57C747.2020104@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox