From: mariano.lopez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Cc: paul.eggleton@linux.intel.com
Subject: [PATCHv3 0/6] Create image manifest
Date: Thu, 19 Nov 2015 14:25:13 +0000 [thread overview]
Message-ID: <cover.1447942163.git.mariano.lopez@linux.intel.com> (raw)
From: Mariano Lopez <mariano.lopez@linux.intel.com>
When building the rootfs the rootfs is created but the recipes
that deployed files in the image doesn't show up. Usually these
recipes include the bootloaders and the kernel.
With these patches a new manifest will be created that includes
the deployed recipes that were in the deployed. The format of the
manifest is different because the recipes doesn't install packages,
instead the recipes deploy files into the image
[YOCTO #6772]
Changes in v3:
- Create recipinfo file in every license folder to have the required
information for the manifest file without using PKGDATA
The following changes since commit 1b25a70991589ed1f123015c16ee4806c46e3199:
yocto-project-qs, ref-manual, poky.ent: CentOS Package updates (2015-11-18 16:42:22 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib mariano/bug6772v3
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mariano/bug6772v3
Mariano Lopez (6):
license.bbclass: Write recipeinfo file in license folder
license.bbclass: Split license create manifest
license.bbclass: Added get_boot_dependencies function
license.bbclass: Added function get_deployed_dependencies
license.bbclass: Add function get_deployed_files
license.bbclass: Create image license manifest
meta/classes/license.bbclass | 207 +++++++++++++++++++++++++++++++++++++------
1 file changed, 182 insertions(+), 25 deletions(-)
--
1.8.4.5
next reply other threads:[~2015-11-19 22:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 14:25 mariano.lopez [this message]
2015-11-19 14:25 ` [PATCHv3 1/6] license.bbclass: Write recipeinfo file in license folder mariano.lopez
2015-11-20 2:32 ` Paul Eggleton
2015-11-19 14:25 ` [PATCHv3 2/6] license.bbclass: Split license create manifest mariano.lopez
2015-11-19 14:25 ` [PATCHv3 3/6] license.bbclass: Added get_boot_dependencies function mariano.lopez
2015-11-20 2:33 ` Paul Eggleton
2015-11-19 14:25 ` [PATCHv3 4/6] license.bbclass: Added function get_deployed_dependencies mariano.lopez
2015-11-19 14:25 ` [PATCHv3 5/6] license.bbclass: Add function get_deployed_files mariano.lopez
2015-11-20 2:33 ` Paul Eggleton
2015-11-19 14:25 ` [PATCHv3 6/6] license.bbclass: Create image license manifest mariano.lopez
[not found] ` <cover.1448015777.git.mariano.lopez@linux.intel.com>
2015-11-20 10:44 ` [PATCHv4 1/6] license.bbclass: Write recipeinfo file in license folder mariano.lopez
2015-11-20 10:44 ` [PATCHv4 2/6] license.bbclass: Split license create manifest mariano.lopez
2015-11-20 10:44 ` [PATCHv4 3/6] license.bbclass: Added get_boot_dependencies function mariano.lopez
2015-11-20 10:44 ` [PATCHv4 4/6] license.bbclass: Added function get_deployed_dependencies mariano.lopez
2015-11-20 10:44 ` [PATCHv4 5/6] license.bbclass: Add function get_deployed_files mariano.lopez
2015-11-20 10:44 ` [PATCHv4 6/6] license.bbclass: Create image license manifest mariano.lopez
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=cover.1447942163.git.mariano.lopez@linux.intel.com \
--to=mariano.lopez@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