Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] gstreamer: Remove machine specific append
Date: Thu, 18 Oct 2018 11:28:13 +0100	[thread overview]
Message-ID: <3c135d27d6897c3802700438fd58eec85630d76d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20181017164326.67111-5-mark.hatle@windriver.com>

On Wed, 2018-10-17 at 12:43 -0400, Mark Hatle wrote:
> If you try to build a system with multiple BSPs, one of which is qemux86
> or qemux86-64, the gstreamer package will change.  This will trigger
> anything using gstream to also be rebuilt.
> 
> For a package based system, the PR values will also be incremented each
> time.  The end result will be an ever growing set of PR values as well as
> being unable to tell which configured version of the multimedia components
> are really being deployed.
> 
> The solution here was to remove the rrecommend for consistency.
> 
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
>  meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.2.bb | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.2.bb b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.2.bb
> index 7f291f6630..3a6e53de04 100644
> --- a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.2.bb
> +++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.14.2.bb
> @@ -55,8 +55,6 @@ FILES_${PN} += "${libdir}/gstreamer-1.0/*.so"
>  FILES_${PN}-dev += "${libdir}/gstreamer-1.0/*.la ${libdir}/gstreamer-1.0/*.a ${libdir}/gstreamer-1.0/include"
>  FILES_${PN}-bash-completion += "${datadir}/bash-completion/completions/ ${datadir}/bash-completion/helpers/gst*"
>  
> -RRECOMMENDS_${PN}_qemux86 += "kernel-module-snd-ens1370 kernel-module-snd-rawmidi"
> -RRECOMMENDS_${PN}_qemux86-64 += "kernel-module-snd-ens1370 kernel-module-snd-rawmidi"
>  RDEPENDS_${PN}-ptest += "make"


We can't just delete these, they need moving to the machine conf files
instead. Since we need to build M4 soon and this is a problem, I've put
a patch into master-next which does this for testing.

Cheers,

Richard




      reply	other threads:[~2018-10-18 10:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 16:43 [PATCH 0/4] Fix a number of non-machine pkg hash change issues Mark Hatle
2018-10-17 16:43 ` [PATCH 1/4] systemd: Remove items that made this machine (qemu) specific Mark Hatle
2018-10-18  8:53   ` ChenQi
2018-10-18 15:37     ` Mark Hatle
2018-10-18 22:57   ` Richard Purdie
2018-10-20  8:41   ` Richard Purdie
2018-10-20 16:14     ` Mark Hatle
2018-10-17 16:43 ` [PATCH 2/4] mesa: Remove machine specific append Mark Hatle
2018-10-17 16:43 ` [PATCH 3/4] weston: " Mark Hatle
2018-10-18 10:24   ` Burton, Ross
2018-10-18 15:38     ` Mark Hatle
2018-10-19 10:51       ` Burton, Ross
2018-10-24 10:13         ` Mark Hatle
2018-10-25  8:36     ` Alexander Kanavin
2018-10-25  9:05       ` Martin Jansa
2018-10-25  9:26       ` Richard Purdie
2018-10-17 16:43 ` [PATCH 4/4] gstreamer: " Mark Hatle
2018-10-18 10:28   ` 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=3c135d27d6897c3802700438fd58eec85630d76d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox