Hi Diane,
Diane Trout <di...@debian.org> wrote:
I was packaging libaccounts-glib for the KDE team and Scott Kitterman
noticed
a ./usr/lib/python2.7/dist-packages/gi/overrides/Accounts.py (and
python3
version) in gir1.2-accounts-1.0. I saw you're the maintainer for
python-gi and
probably understand how the gi/override is supposed to work.
He thinks I should add a python dependency for the package, I think
that the
Accounts.py is incidental to the operation of a gir1.2 package, as I
understand it typelibs can be used by other languages.
I was hoping you could weigh in what the gi/override directory is for,
and if
gir1.2- packages that contain a gi/override should have a dependency on
python?
I think you are right. The Python override is only used by Python
packages, but if a package in another language makes use of the GI
module, it will not need that file.
So the package doesn’t strictly need a Python dependency. On the other
hand, lacking ${python:Depends} will mean it will lack the required
dependencies to trigger an upgrade when the default Python version
changes.
(And just in general is there documentation about how typelibs work?
I've had
some trouble finding it)
The GI policy is a good starting point:
/usr/share/doc/gobject-introspection/policy.txt
--
Joss
