From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH] dbus: split X11 dependant dbus-launch into its own subpackage
Date: Wed, 25 May 2011 14:49:37 -0700 [thread overview]
Message-ID: <4DDD7971.5060703@linux.intel.com> (raw)
In-Reply-To: <1306359819.27470.68.camel@rex>
On 05/25/2011 02:43 PM, Richard Purdie wrote:
> On Wed, 2011-05-25 at 22:18 +0200, Koen Kooi wrote:
>> This makes dbus usable in non-X enviroments like QT/e
>>
>> From the original commit in OE .dev:
>>
>> commit 8e25448fb01b6fa6ea3a86f9327f080cd753dfbc
>> Author: John Lee<john_lee@openmoko.org>
>> Date: Fri Sep 5 11:37:39 2008 +0000
>>
>> dbus: enable x support and put dbus-launch into new package dbus-x11
>> * Enable x support only add rdepends to dbus-launch. Make it a
>> seperate package so other packages like dbus does not rdepend on
>> libx11.
>
> Which pieces of the system use dbus-launch and do we need to add
> dependencies to them after this change to pull in the dbus-x11 package?
>
Richard there is a patch from Khem back on 5/7 that replaces gconf-dbus
but did not have all the parts in place, I think this is the first steps
to getting the parts in place to beable to untangle the gconf dbus stuff
Sau!
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-05-25 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 20:18 [PATCH] dbus: split X11 dependant dbus-launch into its own subpackage Koen Kooi
2011-05-25 21:43 ` Richard Purdie
2011-05-25 21:49 ` Saul Wold [this message]
2011-05-25 22:43 ` Richard Purdie
2011-05-26 6:39 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 19:47 Koen Kooi
[not found] ` <1306353358.3120.29.camel@lenovo.internal.reciva.com>
2011-05-25 20:18 ` 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=4DDD7971.5060703@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.