All of lore.kernel.org
 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] gst-meta-base: Make ximagesing optional on x11 DISTRO_FEATURE
Date: Wed, 28 Nov 2012 06:51:11 +0000	[thread overview]
Message-ID: <1354085471.21863.124.camel@ted> (raw)
In-Reply-To: <1353910511-12931-1-git-send-email-sgw@linux.intel.com>

On Sun, 2012-11-25 at 22:15 -0800, Saul Wold wrote:
> If x11 is disabled from DISTRO_FEATURE we don't build the ximagesink
> package, but it still becomes a dependency in the final image which
> causes a failure
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  .../gstreamer/gst-meta-base_0.10.bb                |    3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb b/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
> index 2fb39d5..0889437 100644
> --- a/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
> +++ b/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
> @@ -16,7 +16,10 @@ PACKAGES = "\
>  
>  ALLOW_EMPTY = "1"
>  
> +X11_RDEPENDS = "${@base_contains('DISTRO_FEATURES', 'x11', 'gst-plugin-base-ximagesink', '', d)}"
> +
>  RDEPENDS_gst-meta-base = "\
> +    ${X11_RDEPENDS} \
>      gstreamer \
>      gst-plugins-base-playbin \
>      gst-plugins-base-decodebin \

This doesn't make sense, surely there would be some removal of a
dependency as well as an addition?

Looking at the recipe, the ximagesink dependency is already dependent on
DISTRO_FEATURES and is in the gst-meta-x11-base package, not
gst-meta-base?

Cheers,

Richard




      parent reply	other threads:[~2012-11-28  7:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26  6:15 [PATCH] gst-meta-base: Make ximagesing optional on x11 DISTRO_FEATURE Saul Wold
2012-11-28  1:14 ` Saul Wold
2012-11-28  6:51 ` 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=1354085471.21863.124.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 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.