All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Help debug QA foo rdepends on bar-dev
Date: Fri, 25 May 2012 09:25:50 -0700	[thread overview]
Message-ID: <4FBFB28E.3090507@linux.intel.com> (raw)
In-Reply-To: <cover.1337886141.git.mark.hatle@windriver.com>

On 05/24/2012 12:11 PM, Mark Hatle wrote:
> After numerous attempts to try to remotely help people stuck by the QA test
> that a base package requires a -dev package, I needed to figure out a way
> to add diagnostics to the logs to help identify what was happening.
>
> The patch adds some basic diagnostics to indicate what dependency was found
> and what package it triggered to be added to the rdepends.
>
> In addition it was observed that a lot of duplicate processing was occuring
> so I modifed the system to eliminate the duplicates.  This has the potential
> to improve performance, but I was not able to measure anything statistically
> significant in my builds.
>
> The following changes since commit 0f795f81fe5ad3ef78c21a177eca90fbc8810f81:
>
>    qemu: disable vnc-jpeg compression (2012-05-24 08:53:40 +0100)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib mhatle/package
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/package
>
> Mark Hatle (1):
>    package.bbclass: Add additional debugging for dependencies
>
>   meta/classes/package.bbclass |    7 +++++--
>   1 files changed, 5 insertions(+), 2 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-05-25 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 19:11 [PATCH 0/1] Help debug QA foo rdepends on bar-dev Mark Hatle
2012-05-24 19:11 ` [PATCH 1/1] package.bbclass: Add additional debugging for dependencies Mark Hatle
2012-05-25 16:25 ` Saul Wold [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=4FBFB28E.3090507@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.