Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dbus: remove uneeded RDEPENDS on ptest
Date: Fri, 22 Mar 2013 16:24:22 +0000	[thread overview]
Message-ID: <1363969462.3097.15.camel@ted> (raw)
In-Reply-To: <1363909196-10482-1-git-send-email-sgw@linux.intel.com>

On Thu, 2013-03-21 at 16:39 -0700, Saul Wold wrote:
> This solves a multiple provider issue along with a build failure with ptest enabled
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/recipes-core/dbus/dbus.inc | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
> index affffbc..a1b56a5 100644
> --- a/meta/recipes-core/dbus/dbus.inc
> +++ b/meta/recipes-core/dbus/dbus.inc
> @@ -9,8 +9,6 @@ X11DEPENDS = "virtual/libx11 libsm"
>  DEPENDS = "expat virtual/libintl ${@base_contains('DISTRO_FEATURES', 'x11', '${X11DEPENDS}', '', d)}"
>  DEPENDS_class-native = "expat-native virtual/libintl-native"
>  DEPENDS_class-nativesdk = "nativesdk-expat virtual/nativesdk-libintl"
> -RDEPENDS_dbus = "${@base_contains('DISTRO_FEATURES', 'ptest', 'dbus-ptest', '', d)}"
> -RDEPENDS_class-native = ""
>  
>  INC_PR = "r6"

We need to fix this but the idea was to trigger a dependency on
dbus-ptest being built, if dbus was built...

Cheers,

Richard





  reply	other threads:[~2013-03-22 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 23:39 [PATCH] dbus: remove uneeded RDEPENDS on ptest Saul Wold
2013-03-22 16:24 ` Richard Purdie [this message]
2013-03-25 14:24   ` [PATCH 1/2] dbus: Depend on dbus-ptest-ptest Björn Stenberg
2013-03-25 14:26     ` Björn Stenberg

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=1363969462.3097.15.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@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