From: Robert Yang <liezhi.yang@windriver.com>
To: Koen Kooi <koen@dominion.thruhere.net>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install
Date: Mon, 13 Jan 2014 10:00:05 +0800 [thread overview]
Message-ID: <52D348A5.6080808@windriver.com> (raw)
In-Reply-To: <8DE9C4FF-2468-4BE0-9FF3-8DC428F5A762@dominion.thruhere.net>
On 01/09/2014 02:33 PM, Koen Kooi wrote:
>
> Op 8 jan. 2014, om 17:12 heeft Burton, Ross <ross.burton@intel.com> het volgende geschreven:
>
>> On 7 January 2014 13:05, Robert Yang <liezhi.yang@windriver.com> wrote:
>>>> *Some* packages have migrated away from gconf to gsettings. Not all
>>>> packages have done this, so anything still using gconf is now broken.
>>>> Note that almost nothing in oe-core uses gsettings as we're still
>>>> using the GTK+ 2 stack generally.
>>>
>>> Hi Ross, which recipe is failed, please ?
>>
>> A better question would be what package did you get this warning from?
>>
>> As I said, any recipe that did inherit gnome and still used GConf
>> would be affected by your change.
>
> Which is over half of the meta-gnome recipes :(
>
Sounds bad, fortunately, it had been reverted.
// Robert
next prev parent reply other threads:[~2014-01-13 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 17:27 [PATCH 0/2] fix unrecognised options Robert Yang
2014-01-03 17:27 ` [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install Robert Yang
2014-01-06 15:47 ` Burton, Ross
2014-01-07 13:05 ` Robert Yang
2014-01-08 16:12 ` Burton, Ross
2014-01-09 6:33 ` Koen Kooi
2014-01-13 2:00 ` Robert Yang [this message]
2014-01-03 17:27 ` [PATCH 2/2] mime.bbclass: remove the --disable-update-mimedb Robert Yang
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=52D348A5.6080808@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=koen@dominion.thruhere.net \
--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 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.