All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Phil Blundell <pb@pbcl.net>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] alsa-utils: Move alsaconf to its own recipe
Date: Mon, 29 Apr 2013 14:54:29 +0100	[thread overview]
Message-ID: <1367243669.5379.21.camel@ted> (raw)
In-Reply-To: <1366894048.14512.87.camel@phil-desktop.brightsign>

On Thu, 2013-04-25 at 13:47 +0100, Phil Blundell wrote:
> 18575b082a4042376fd1575465e69562dea04ddc added bash as a dependency of
> alsa-utils-alsaconf so that the script interpreter will be available at
> run time.  However, this has the undesirable side effect of making bash
> be a build dependency for alsa-utils and, for those folks who don't need
> alsaconf but do want some other part of alsa-utils, this cure is worse
> than the original disease.
> 
> Fix this by moving alsaconf to a separate recipe so that the bash
> dependency only applies when alsaconf is specifically requested.
> 
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---
>  .../alsa/alsa-utils-alsaconf_1.0.26.bb             |   22 ++++++++++++++++++++
>  meta/recipes-multimedia/alsa/alsa-utils_1.0.26.bb  |   12 +++++++----
>  2 files changed, 30 insertions(+), 4 deletions(-)
>  create mode 100644 meta/recipes-multimedia/alsa/alsa-utils-alsaconf_1.0.26.bb

I merged this however I'm not convinced its the right way to handle
this. I'm wondering about a PACKAGECONFIG which when turned off, deletes
alsaconf. I suspect that might be a nicer way to handle this kind of
issue going forward...

Cheers,

Richard






  parent reply	other threads:[~2013-04-29 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 12:47 [PATCH] alsa-utils: Move alsaconf to its own recipe Phil Blundell
2013-04-25 20:58 ` Saul Wold
2013-04-26 13:03   ` Phil Blundell
2013-04-29 13:54 ` Richard Purdie [this message]
2013-04-29 14:03   ` Phil Blundell
2013-04-29 14:50   ` Koen Kooi

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=1367243669.5379.21.camel@ted \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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.