Created attachment 193325 [details] enable-introspection Was set: USE_GNOME= glib20 introspection:build,run But was: CONFIGURE_ARGS= --disable-docs --disable-introspection --with-ffi And some python app was required py-gobject with introspection.
testbuilds are fine. Anyone with more gnome clue able to comment on that change ?
(In reply to rozhuk.im from comment #0) Shouldn't python apps use pygobject3 instead? It is already available in ports as devel/py-gobject3. pygobject3 is compatible with both python2 and python3.
pygobject3 is @3.18.2 in the ports tree, and 3.29.1 upstream, if I look at this: https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS Does anyone know why it's not nearer to upstream ?
(In reply to Kurt Jaeger from comment #3) The latest stable pygobject release is 3.28.2. Most GNOME projects use odd minor version numbers to indicate unstable releases. The reason of keeping outdated releases in ports is that our x11/gnome3 is still at 3.18. GNOME ports are usually updated together, so the current problem is that we failed to catch up with upstream. It doesn't mean that we have to wait for GNOME 3.28 upgrade to happen to update pygobject to 3.28 releases. It usually means there is currently no ports requiring pygobject > 3.18 so nobody requests an update for it.
(In reply to Ting-Wei Lan from comment #2) I am not python programmer, so I just give program that it require to run. Also python 2.7 already installed as dep for many ports, and python 3.6 does not installed.
(In reply to rozhuk.im from comment #5) It doesn't matter whether you are a python programmer. If a python app has 'import gi' or 'from gi.repository import Something', it uses gobject-introspection-based bindings and you have to use devel/py-gobject3 to satisfy the dependency instead of devel/py-gobject.
Ting-Wei Lan right, also after patch this port conflict with devel/py-gobject3.