Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] connman: ensure ofono package is generated.
Date: Mon, 09 Apr 2012 14:21:39 -0700	[thread overview]
Message-ID: <4F8352E3.1040902@linux.intel.com> (raw)
In-Reply-To: <af03fd7f8452c7795fce23e3276e456dc431266f.1333693070.git.lianhao.lu@intel.com>

On 04/05/2012 11:20 PM, Lianhao Lu wrote:
> Make sure ofono package is generated when buidling connman, because
> dynamic package connman-plugin-ofono has a RDEPENDS on ofono.
>
Since this is for a plugin, can the connman-plugin-ofono be generated in 
a separate package (or possibly even a separate recipe that depends on 
ofono, instead of making connman depend on ofono, I am not sure the 
solution below is correct either.

Sau!

> Signed-off-by: Lianhao Lu<lianhao.lu@intel.com>
> ---
>   meta/recipes-connectivity/connman/connman.inc |    2 ++
>   1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-connectivity/connman/connman.inc b/meta/recipes-connectivity/connman/connman.inc
> index 1a6dd1b..3ed5667 100644
> --- a/meta/recipes-connectivity/connman/connman.inc
> +++ b/meta/recipes-connectivity/connman/connman.inc
> @@ -39,6 +39,8 @@ EXTRA_OECONF += "\
>       --disable-ntpd \
>   "
>
> +do_package[depends] = "${MLPREFIX}ofono:do_package"
> +
>   INITSCRIPT_NAME = "connman"
>   INITSCRIPT_PARAMS = "start 05 5 2 3 . stop 22 0 1 6 ."
>



  reply	other threads:[~2012-04-09 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  6:19 [PATCH 0/1] Ensure package dependency between connman and ofono Lianhao Lu
2012-04-06  6:20 ` [PATCH 1/1] connman: ensure ofono package is generated Lianhao Lu
2012-04-09 21:21   ` Saul Wold [this message]
2012-04-10  3:03     ` Lu, Lianhao

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=4F8352E3.1040902@linux.intel.com \
    --to=sgw@linux.intel.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