From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Core image recipes
Date: Fri, 26 Aug 2011 10:47:10 +0100 [thread overview]
Message-ID: <201108261047.10782.paul.eggleton@linux.intel.com> (raw)
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
meta/recipes-extended/images/core-image-basic.bb
Maybe we could just have one of these and call it core-image-x11-base or
similar?
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.
Comments?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2011-08-26 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 9:47 Paul Eggleton [this message]
2011-08-26 16:18 ` Core image recipes Saul Wold
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=201108261047.10782.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox