From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Alex Franco <alejandro.franco@linux.intel.com>,
openembedded-core@lists.openembedded.org
Cc: paul.eggleton@linux.intel.com
Subject: Re: [PATCH 0/3] Empty-image functionality
Date: Fri, 28 Aug 2015 13:23:23 -0500 [thread overview]
Message-ID: <55E0A71B.5040504@linux.intel.com> (raw)
In-Reply-To: <1440626255-29614-1-git-send-email-alejandro.franco@linux.intel.com>
Acked-by: Aníbal Limón <anibal.limon@linux.intel.com>
On 26/08/15 16:57, Alex Franco wrote:
> Enable creation of core-empty-image (a recipe that inherits image
> without any extra packages) or similar empty images, whether RPM,
> DEB or IPK packaging is selected.
>
> [YOCTO #7664]
>
> Alex Franco (3):
> Empty image: core-image-empty recipe, Rootfs fix
> Empty image: package list splitting and iteration
> Empty image: filesystem allocation
>
> meta/classes/image_types.bbclass | 10 +++++++++-
> meta/classes/license.bbclass | 2 +-
> meta/lib/oe/package_manager.py | 5 +++--
> meta/lib/oe/rootfs.py | 8 ++++++--
> meta/recipes-core/images/core-image-empty.bb | 7 +++++++
> 5 files changed, 26 insertions(+), 6 deletions(-)
> create mode 100644 meta/recipes-core/images/core-image-empty.bb
>
prev parent reply other threads:[~2015-08-28 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 21:57 [PATCH 0/3] Empty-image functionality Alex Franco
2015-08-26 21:57 ` [PATCH 1/3] Empty image: core-image-empty recipe, Rootfs fix Alex Franco
2015-08-29 11:18 ` Paul Eggleton
2015-09-08 23:20 ` Alex Franco
2015-08-26 21:57 ` [PATCH 2/3] Empty image: package list splitting and iteration Alex Franco
2015-08-26 21:57 ` [PATCH 3/3] Empty image: filesystem allocation Alex Franco
2015-09-11 17:26 ` Benjamin Esquivel
2015-09-11 22:32 ` Richard Purdie
2015-08-28 18:23 ` Aníbal Limón [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=55E0A71B.5040504@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=alejandro.franco@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