From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Daniel Lazzari <dlazzari@leapfrog.com>
Subject: Re: [PATCH 1/1] Fix alsa-utils package dependencies
Date: Wed, 21 Sep 2011 15:57:52 -0700 [thread overview]
Message-ID: <4E7A6BF0.2080709@linux.intel.com> (raw)
In-Reply-To: <E7A9054A5ACABE48B0E540E46E862B0F012064@NAEMMAIL01.na.leapfrog.com>
On 09/20/2011 04:15 PM, Daniel Lazzari wrote:
> Make alsa-utils main package depend on all of the more specific alsa-utils packages (such as alsa-utils-alsamixer).
>
> Signed-off-by: Daniel Lazzari Jr<dlazzari@leapfrog.com>
> ---
> .../recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb b/meta/recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb
> index 52a7871..307f293 100644
> --- a/meta/recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb
> +++ b/meta/recipes-multimedia/alsa/alsa-utils_1.0.24.2.bb
> @@ -28,7 +28,7 @@ inherit autotools gettext
> # This are all packages that we need to make. Also, the now empty alsa-utils
> # ipk depends on them.
>
> -PACKAGES += "\
> +ALSA_UTILS_PKGS = "\
> alsa-utils-alsamixer \
> alsa-utils-midi \
> alsa-utils-aplay \
> @@ -44,6 +44,9 @@ PACKAGES += "\
> alsa-utils-alsaucm \
> "
>
> +PACKAGES += "${ALSA_UTILS_PKGS}"
> +RDEPENDS_${PN} += "${ALSA_UTILS_PKGS}"
> +
> # We omit alsaconf, because
> # a) this is a bash script
> # b) it creates config files not suitable for OE-based distros
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-09-21 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 23:15 [PATCH 1/1] Fix alsa-utils package dependencies Daniel Lazzari
2011-09-21 22:57 ` 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=4E7A6BF0.2080709@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dlazzari@leapfrog.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