summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/initscripts/initscripts_1.0.bb
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-01-06 16:28:53 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-01-06 16:30:28 +0000
commitf4ae4399140ef61bafdd9223583a249279959ae1 (patch)
treebd88266c6771b3d734946924f7ed722e3cbecbc0 /meta/recipes-core/initscripts/initscripts_1.0.bb
parent2ee78e3ac45f220dddeb75e4436b114bb983d4ef (diff)
downloadpoky-f4ae4399140ef61bafdd9223583a249279959ae1.tar.gz
Revert "gconf.bbclass: remove --disable-schemas-install"
This reverts commit 84fa245b1d1e7935094e3b8a452d69461dc3dcbb. Ross Burton comments that: *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. The problem is that people are using gnome.bbclass which is a kitchen sink class, inheriting many other classes that may or may not be used. To resolve this warning gnome.bbclass should extend the sanity check whitelist with --disable-schemas-install as it is the class causing gconf.bbclass to be inherited on recipes that don't use gconf. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/initscripts/initscripts_1.0.bb')
0 files changed, 0 insertions, 0 deletions