All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 1/5] alsa-plugins: initial recipe
Date: Sun, 24 May 2015 07:25:58 +0100	[thread overview]
Message-ID: <1432448758.12832.67.camel@linuxfoundation.org> (raw)
In-Reply-To: <e5260dbf168f3c51d9114e4c4cb1fca49abc83b1.1432320274.git.tanu.kaskinen@linux.intel.com>

On Fri, 2015-05-22 at 21:51 +0300, Tanu Kaskinen wrote:
> When PulseAudio is installed, alsa-plugins is needed to provide
> compatibility for ALSA applications.
> 
> The dependencies are set up so that pulseaudio-server depends on
> alsa-plugins-pulseaudio-conf, and alsa-plugins-pulseaudio-conf depends
> on the PulseAudio plugins. This should make the ALSA->PulseAudio
> compatibility configuration work out of the box, while leaving the
> PulseAudio specific configuration out on systems that don't have
> pulseaudio-server installed.
> 
> The alsa-plugins recipes in meta-guacamayo and meta-webos were used as
> references, but this recipe is not a straight copy of either.
> 
> Signed-off-by: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>

FWIW this new recipe failed on the autobuilder when it was tested in a
multilib build:

ERROR: QA Issue: lib32-alsa-plugins: Files/directories were installed
but not shipped in any package:
  /usr/lib32/alsa-lib/libasound_module_rate_speexrate_medium.so
  /usr/lib32/alsa-lib/libasound_module_rate_samplerate_order.so
  /usr/lib32/alsa-lib/libasound_module_rate_samplerate_medium.so
  /usr/lib32/alsa-lib/libasound_module_rate_samplerate_best.so
  /usr/lib32/alsa-lib/libasound_module_rate_samplerate_linear.so
  /usr/lib32/alsa-lib/libasound_module_rate_speexrate_best.so
Please set FILES such that these items are packaged. Alternatively if
they are unneeded, avoid installing them or delete them within
do_install. [installed-vs-shipped]

I created a follow up patch:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t222&id=bd4f5e346550f961f7a1056661f9b9fefdc8fff6

which fixed this and meant to merge it immediately after your commit
however it looks like I squashed the patches accidentally. In comes down
to the class extension code not being able to rewrite entries from
PACKAGES_DYNAMIC.

Cheers,

Richard



  reply	other threads:[~2015-05-24  6:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 18:51 [PATCH v3 0/5] Enable PulseAudio in Sato images Tanu Kaskinen
2015-05-22 18:51 ` [PATCH v3 1/5] alsa-plugins: initial recipe Tanu Kaskinen
2015-05-24  6:25   ` Richard Purdie [this message]
2015-05-28  4:19     ` Khem Raj
2015-05-28  4:48       ` Khem Raj
2015-06-03 11:18         ` Tanu Kaskinen
2015-06-04  4:52           ` Khem Raj
2015-05-22 18:51 ` [PATCH v3 2/5] pulseaudio: client-conf: Add allow-autospawn-for-root Tanu Kaskinen
2015-05-22 18:51 ` [PATCH v3 3/5] pulseaudio: conf-parser: add support for .d directories Tanu Kaskinen
2015-05-22 18:51 ` [PATCH v3 4/5] pulseaudio-client-conf-sato: initial recipe Tanu Kaskinen
2015-05-22 18:51 ` [PATCH v3 5/5] packagegroup-core-x11-sato: add PulseAudio Tanu Kaskinen

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=1432448758.12832.67.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tanu.kaskinen@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.