Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH RFC 1/3] insane: Split do_package_qa into a separate task (from do_package)
Date: Fri, 11 Jul 2014 22:11:37 +0100	[thread overview]
Message-ID: <1405113097.21289.93.camel@ted> (raw)
In-Reply-To: <CAJTo0LZ0BD76LshHyfBMwKU0tgqS+3_QT1LZpLxbX4n03ZCmWA@mail.gmail.com>

On Fri, 2014-07-11 at 20:37 +0100, Burton, Ross wrote:
> On 11 July 2014 14:22, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > The anonymous python fragment should be fine, it sets the data at the
> > right level, the global recipe level rather than burying it in some
> > task.
> 
> FWIW this broke the X drivers as they inject dependencies in
> populate_packages_prepend().  It's probably worth reviewing all
> instances of populate_packages_prepend() in oe-core at least as I
> clearly copied using that hook from someone else...

It shouldn't have broken the dependencies, you can still inject things
there and that has not changed.  If that has stopped working, there is
something else wrong.

What you can't now do is change the package QA process through
populate_packages but that makes much less sense.

Cheers,

Richard



  parent reply	other threads:[~2014-07-11 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 20:15 [PATCH RFC 1/3] insane: Split do_package_qa into a separate task (from do_package) Richard Purdie
2014-07-11  2:43 ` Otavio Salvador
2014-07-11  8:27   ` Richard Purdie
2014-07-11 12:14     ` Otavio Salvador
2014-07-11 13:22       ` Richard Purdie
2014-07-11 16:46         ` Otavio Salvador
2014-07-11 17:40           ` Richard Purdie
2014-07-11 19:37         ` Burton, Ross
2014-07-11 19:46           ` Otavio Salvador
2014-07-11 21:11           ` Richard Purdie [this message]
2014-07-18 10:26   ` Martin Jansa

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=1405113097.21289.93.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=meta-freescale@yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=ross.burton@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