Iñaki

Hi! Thanks for the report, and sorry for the slow reply! I didn't have the time to look into this until now. I don't think that you are doing anything...

> In the meantime I have started creating cli tool for haskell-gi, allowing me to inspect the gir info from commandline and view generated binding, wrapper code and Gi AST....

(Forgot to say: if fixing that by hand fixes the issue it will be easy to add some overrides that do it in the bindings themselves.)

Thanks for the report. I am a little bit confused. The `gi-*` packages do not depend directly on `gobject-introspection`, no? As far as I can tell (I would be glad...

Oh, I think I see what's going on now, thanks. The issue is that when generating the bindings for `gi-atk` we also try to load the gir info for dependencies...

Thanks for the PR! It looks almost perfect, and I would be happy to merge once the CI passes. The failure in the CI comes from missing dependencies in the...

I think that the introspection annotation is wrong. Could you please check if the following steps fix the issue? 1. Copy `/usr/share/gir-1.0/Dazzle-1.0.gir` somewhere you have write access, say `/home/adamsmd/tmp`. 2....

Hi! I would not mind in principle (certainly not if this is really needed for packaging to be possible at all!), but I would like to understand the situation better,...

Thanks for the comments! I am still a bit unclear, sorry. Is it technically not possible to have separate gi-gtk4.spec and gi-gtk3.spec files that wrap different versions of the same...

Just a thought: even if it's a little confusing, keeping `gi-gtk` generic (having both `3.0.x` and `4.0.x` versions) and then having specific version restricted variants as you suggest might work....