From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pulseaudio: Added consolekit dependency for pulseaudio-module-console-kit package
Date: Thu, 11 Jul 2013 13:20:10 +0100 [thread overview]
Message-ID: <2680058.xDZ0dG4UEH@helios> (raw)
In-Reply-To: <CAJTo0LZ7POY-i61qz8hUE=JXbc0=0uoNo_i1aTmgi-ma_cc8hw@mail.gmail.com>
On Thursday 11 July 2013 11:32:14 Burton, Ross wrote:
> On 10 July 2013 19:50, Saul Wold <sgw@linux.intel.com> wrote:
> > Is this really a build-time dependency or a runtime dependency specific to
> > the pulseaudio-module?
>
> It's a runtime dependency, but from memory bitbake doesn't manage to
> piece the chain together enough to actually build consolekit (probably
> because the packages are dynamically created).
If it's a stated RDEPENDS in the recipe it must be, and pulseaudio.inc already
has RDEPENDS_pulseaudio-module-console-kit =+ "consolekit" so unless the
module package doesn't actually end up being "pulseaudio-module-console-kit"
I'm not sure why anything else should be needed. It's usually only when the
dependencies get added dynamically at package time that bitbake not building a
dependency can be a problem (we've seen this with recipes containing perl
scripts for example).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-11 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 17:16 [PATCH] pulseaudio: Added consolekit dependency for pulseaudio-module-console-kit package eu
2013-07-10 18:50 ` Saul Wold
2013-07-11 10:32 ` Burton, Ross
2013-07-11 12:20 ` Paul Eggleton [this message]
2013-07-11 12:26 ` Martin Jansa
2013-07-16 22:07 ` Felipe Tonello
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=2680058.xDZ0dG4UEH@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox