All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] task-fso-compliance: depend on fso-abyss
Date: Fri, 26 Mar 2010 01:06:05 +0100	[thread overview]
Message-ID: <1269561965.3252.26.camel@opal> (raw)
In-Reply-To: <1269555678-8427-1-git-send-email-ospite@studenti.unina.it>

> diff --git a/recipes/tasks/task-fso-compliance.bb b/recipes/tasks/task-fso-compliance.bb
> index e1776a8..50230f0 100644
> --- a/recipes/tasks/task-fso-compliance.bb
> +++ b/recipes/tasks/task-fso-compliance.bb
> @@ -2,7 +2,7 @@ DESCRIPTION = "The freesmartphone.org framework -- install this task to make you
>  SECTION = "fso/base"
>  LICENSE = "MIT"
>  PV = "1.0"
> -PR = "r8"
> +PR = "r9"
>  
>  inherit task
>  
> @@ -12,6 +12,7 @@ RDEPENDS_${PN} = "\
>  #  fso-apmd \
>    fso-gpsd \
>  #  fso-monitord \
> +  fso-abyss \
>    connman \
>    connman-scripts \
>  #  connman-plugin-bluetooth \

That's wrong, fso-abyss is only used for some of the machines (i.e.
Openmoko ones). Installing it unconditionally only blows up the images.
We should rather find out why something depends on it when you build for
an EZX machine.

:M:





  reply	other threads:[~2010-03-26  0:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 22:21 [PATCH] task-fso-compliance: depend on fso-abyss Antonio Ospite
2010-03-26  0:06 ` Michael 'Mickey' Lauer [this message]
2010-03-26  8:15   ` Antonio Ospite
2010-03-29 15:26     ` Antonio Ospite
2010-03-30 10:23       ` Antonio Ospite
2010-04-01 13:16         ` [PATCH] frameworkd-config-shr: fix a nasty typo Antonio Ospite
2010-04-01 13:23           ` Martin Jansa
2010-04-01 13:34             ` Holger Hans Peter Freyther
2010-04-06 11:13           ` Dr. Michael Lauer

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=1269561965.3252.26.camel@opal \
    --to=mickey@vanille-media.de \
    --cc=openembedded-devel@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 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.