Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] dbus: include dbus-launch in the main dbus package
Date: Thu, 26 Jul 2012 13:36:38 +0300	[thread overview]
Message-ID: <50111DB6.5040506@intel.com> (raw)
In-Reply-To: <CAJTo0LZOq=8kZVZoebfMTauCb=zcdm2ORbq5M4O-GWKETtHJ_Q@mail.gmail.com>

should I create a single patch that changes dbus-x11 to dbus, or one for 
each package?

Radu

On 07/26/2012 01:23 PM, Burton, Ross wrote:
> On 26 July 2012 10:51, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>> What's the point of PROVIDES += dbus-x11, it build fine without it (I'm not questioning the correctness of this, just want to understand the need for it).
>> This morning you said:
>>
>> "it does not build, it complains about nothing providing dbus-x11"
>>
>> That's what the PROVIDES is for.
> Without seeing the logs, I expect the error was when building the
> image.  Nothing will build-depend on dbus-x11 because it isn't a
> source package.
>
> Radu, as a follow-up patch please remove all instances of dbus-x11,
> replacing with dbus if required.
>
> Ross
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2012-07-26 10:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26  6:17 [PATCH v3] dbus: include dbus-launch in the main dbus package Radu Moisan
2012-07-26  6:29 ` Radu Moisan
2012-07-26  8:08   ` Koen Kooi
2012-07-26  8:42     ` Paul Eggleton
2012-07-26  8:43       ` Koen Kooi
2012-07-26  9:18         ` Radu Moisan
2012-07-26  9:51           ` Koen Kooi
2012-07-26 10:23             ` Burton, Ross
2012-07-26 10:36               ` Radu Moisan [this message]
2012-07-26 10:31             ` Radu Moisan
2012-07-26 10:55               ` Radu Moisan
2012-07-26 11:27                 ` Burton, Ross
2012-07-26 11:55                   ` Koen Kooi
2012-07-26 12:00                     ` Burton, Ross
2012-07-26 12:29                       ` Koen Kooi
2012-07-26 12:32                         ` Paul Eggleton
2012-07-26 12:38                           ` Koen Kooi
2012-07-26 12:56                             ` Paul Eggleton
2012-07-26 13:06                               ` Radu Moisan
2012-07-26 13:07                               ` Koen Kooi
2012-07-26 13:12                                 ` Paul Eggleton
2012-07-26 13:21                                   ` Koen Kooi
2012-07-26 12:36                       ` Radu Moisan
2012-07-26 12:51                         ` Koen Kooi
2012-07-26 12:59                           ` Radu Moisan
2012-07-26 13:08     ` Enrico Scholz
2012-07-26 13:24       ` Radu Moisan
2012-07-26 14:32         ` Enrico Scholz
2012-07-26 21:14           ` Burton, Ross
2012-07-26 13:17 ` Enrico Scholz
2012-07-26 21:12   ` Burton, Ross
2012-07-27  6:10     ` Radu Moisan
2012-07-27  6:15       ` Radu Moisan
2012-07-27 10:02       ` Burton, Ross

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=50111DB6.5040506@intel.com \
    --to=radu.moisan@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