Re: [PATCH 00/18] Provide list of deployment artifacts

Otavio Salvador
2016-08-30T10:21:23Z

On Tue, Aug 30, 2016 at 6:29 AM, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
> Hi,
>
> This is a fix for Bug #9869 - Provide a per-target manifest of files which were, or would have been, produced
>
> The list of artifacts produced by deployment tasks (do_deploy, do_image_complete and do_populate_sdk[_ext] is
> obtained from sstate manifests and fired as a TaskArtifacts metadata event. This should allow Toaster to
> handle artifacts in simple way and remove a lot of current Toaster code doing guess work.
>
> To generate manifests for do_image_complete and do_populate_sdk they have been put under sstate control.
>
> To avoid storing big files(images and sdk installer) in sstate new variable SSTATE_SKIP_CREATION has been
> set in image.bbclass and populate_sdk_base.bbclass and sstate code was modified to avoid adding files
> to sstate if SSTATE_SKIP_CREATION is set.

SKIP creation of what? Variable name seems a little vague for me. Even
needing the manifest, does it makes sense to store the image and SDK
on sstate?

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750