Simple solution: add a check for gnome-python-2.0.pc (PKG_CHECK_EXISTS) or include it in COMMON_MODULES.
The gconf python bindings are shipped as part of "gnome-python" module (as named on gnome svn); 'cause gconf is part of GNOME Developer Platform, we can safetly assume that gconf python bindings are available if the pkg-config file for gnome-python is installed. If not, well... change vendor/distro :-)
Simple solution: add a check for gnome-python-2.0.pc (PKG_CHECK_EXISTS) or include it in COMMON_MODULES.
The gconf python bindings are shipped as part of "gnome-python" module (as named on gnome svn); 'cause gconf is part of GNOME Developer Platform, we can safetly assume that gconf python bindings are available if the pkg-config file for gnome-python is installed. If not, well... change vendor/distro :-)