Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: David Reyna <david.reyna@windriver.com>,
	bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] toaster: fix SDK artifact capture
Date: Tue, 11 Apr 2017 12:31:53 +0100	[thread overview]
Message-ID: <1491910313.12091.13.camel@linuxfoundation.org> (raw)
In-Reply-To: <07c4805b646e9c2ff9d9f75febdabcf1c4c3a485.1491800468.git.David.Reyna@windriver.com>

On Sun, 2017-04-09 at 22:07 -0700, David Reyna wrote:
> From: David Reyna <David.Reyna@windriver.com>
> 
> Use the TaskArtifacts event to scan the SDK and ESDK manifests
> to cleanly collect the respective artifact files.
> 
> The previous method was broken when the SDK file deployment moved
> from the do_populate_sdk[_ext] tasks to their sstate tasks. That
> method is disabled (but not yet removed) in preparation for the
> rest of refactor work for the parent #10283 work.
> 
> [YOCTO #10850]
> 
> Signed-off-by: David Reyna <David.Reyna@windriver.com>
> ---
>  bitbake/lib/bb/ui/buildinfohelper.py | 30
> ++++++++++++++++++++++++++++++
>  bitbake/lib/bb/ui/toasterui.py       |  4 +---
>  meta/classes/toaster.bbclass         | 21 ++++++++++++++++-----
>  3 files changed, 47 insertions(+), 8 deletions(-)

This isn't really in the right format, the patches against
toaster.bbclass needs to be sent separately to OE-Core since its in a
separate repository.

I've sorted this out and merged it as we're close to release builds and
I appreciate this needed fixing, please just keep it in mind next time,
thanks!

Richard


      reply	other threads:[~2017-04-11 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  5:07 [PATCH 0/1] toaster: fix SDK artifact capture David Reyna
2017-04-10  5:07 ` [PATCH 1/1] " David Reyna
2017-04-11 11:31   ` Richard Purdie [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=1491910313.12091.13.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=david.reyna@windriver.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