Then after that install I restarted Gimp, and Lua also had namespace
issues... But the Wiki page you pointed to had a similar question and
its answer helped me figure out that somehow the GI_TYPELIB_PATH wasn't
defined. After setting it to:
On 15/06/2020 23:25, Lloyd Konneker via gimp-developer-list wrote:
> I would hope that in the future the Gimp install would define that variable
> in the environment of Gimp so that plugins spawned by Gimp would have the
> same environment. But since 2.99 is still in development, there is no
> installer so you must temporarily do it yourself.
When Gimp is installed as part of the system the typelibs are put in
directories that are already in the GI_TYPELIB_PATH (or in default
On my system, in my shell env, GI_TYPELIB_PATH is not defined. I suppose
you are suggesting the Gimp build (say make install) should set or add to
that variable in my env, but I don't think it should change my .profile.
Maybe the problem is with PyGObject? Are there standard locations (i.e.
paths) for .gir files? Shouldn't PyGObject (and lua-lgi, etc.) be looking
there? Maybe there is no such standard, and to use GI requires the
GI_TYPELIB_PATH variable in the environment.