fix unrecognised options
cover fix unrecognised options
The following changes since commit e3e1d52ca34a975739e79e4baeb28cf04e5e49c2:
bitbake/lib/bb/cooker.py: remove a duplicated self.data (2014-01-04 01:22:32 +0800)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/warning
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/warning
Robert Yang (2):
gconf.bbclass: remove --disable-schemas-install mime.bbclass: remove the --disable-update-mimedb
meta/classes/gconf.bbclass | 6 ------ meta/classes/mime.bbclass | 2 -- 2 files changed, 8 deletions(-)
Signature · 1 line
1.8.3.1
PATCH 1/2 gconf.bbclass: remove --disable-schemas-install
Gnome has moved the schemas to the gsettings-desktop-schemas pkg, so there is no --disable-schemas-install option any more, and we already have the gsettings-desktop-schemas recipe, so remove it, it wil fix the warning:
configure was passed unrecognised options: --disable-schemas-install
--- meta/classes/gconf.bbclass | 6 ------ 1 file changed, 6 deletions(-)
meta/classes/gconf.bbclass +0 -6
@@ -7,12 +7,6 @@ DEPENDS += "gconf gconf-native" export GCONF_SCHEMA_INSTALL_SOURCE = "xml:merged:${STAGING_DIR_NATIVE}${sysconfdir}/gconf/gconf.xml.defaults" export GCONF_BACKEND_DIR = "${STAGING_LIBDIR_NATIVE}/GConf/2" -# Disable install-time schema registration as we're a packaging system so this -# happens in the postinst script, not at install time. Set both the configure -# script option and the traditional envionment variable just to make sure. -EXTRA_OECONF += "--disable-schemas-install" -export GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL = "1" - gconf_postinst() { if [ "x$D" != "x" ]; then export GCONF_CONFIG_SOURCE="xml::$D${sysconfdir}/gconf/gconf.xml.defaults"
Signature · 1 line
1.8.3.1
Re: [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install
Quoted 6 lines · Robert Yang
Gnome has moved the schemas to the gsettings-desktop-schemas pkg, so there is no --disable-schemas-install option any more, and we already have the gsettings-desktop-schemas recipe, so remove it, it wil fix the warning:
configure was passed unrecognised options: --disable-schemas-install
I'd NAK this but it's too late as I see it's been merged.
*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.
Ross
Re: [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install
Quoted 6 lines · Ross
Quoted 5 lines · Robert Yang
Gnome has moved the schemas to the gsettings-desktop-schemas pkg, so there is no --disable-schemas-install option any more, and we already have the gsettings-desktop-schemas recipe, so remove it, it wil fix the warning:
Quoted 9 lines
Quoted 1 line
configure was passed unrecognised options: --disable-schemas-install
I'd NAK this but it's too late as I see it's been merged.
*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 ?
// Robert
Quoted 9 lines
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.Ross
Re: [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install
Quoted 6 lines · Robert Yang
Quoted 4 lines
*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.
Ross
Re: [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install
Op 8 jan. 2014, om 17:12 heeft Burton, Ross <[email protected]> het volgende geschreven:
Quoted 6 lines · Robert Yang
Quoted 5 lines
Quoted 4 lines
*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.
Quoted 6 lines
Quoted 1 line
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 :(
Re: [PATCH 1/2] gconf.bbclass: remove --disable-schemas-install
Quoted 9 lines · Koen Kooi
Op 8 jan. 2014, om 17:12 heeft Burton, Ross <[email protected]> het volgende geschreven:
Quoted 6 lines · Robert Yang
Quoted 5 lines
Quoted 4 lines
*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.
Quoted 9 lines
Quoted 6 lines
Quoted 1 line
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
PATCH 2/2 mime.bbclass: remove the --disable-update-mimedb
In reply to Robert YangGnome and other freedesktop's mime data has been moved to shared-mime-info, and there is no such an option any more, we already have this recipe, so remove it, this will fix the warning:
configure was passed unrecognised options: --disable-update-mimedb
--- meta/classes/mime.bbclass | 2 -- 1 file changed, 2 deletions(-)
meta/classes/mime.bbclass +0 -2
@@ -1,7 +1,5 @@ DEPENDS += "shared-mime-info-native shared-mime-info" -EXTRA_OECONF += "--disable-update-mimedb" - mime_postinst() { if [ "$1" = configure ]; then UPDATEMIMEDB=`which update-mime-database`
Signature · 1 line
1.8.3.1