[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

gobject-introspection’s .typelib files and Multi-Arch

Good morning mentors,

I’m in the process of packaging a GObject–based library[1] which
provides gobject-introspection support.

While preparing the gir1.2- package I stumbled upon the
gobject-introspection mini–policy[2] and found out that .typelib files
are supposed to be installed in the /usr/lib/girepository-1.0 directory,
which doesn’t take multiarch into account.

Seeing as the .typelib files are binary blobs, that sounded odd. I checked
gir1.2-gtk-3.0 for amd64, mipsel and armhf, obtaining this:

  $ md5sum Gtk-3.0.*
  de536efa2a280bd6e41bdc31c6141106  Gtk-3.0.amd64.typelib
  4d35a70e54348924ddfeabf25528089d  Gtk-3.0.armhf.typelib
  4d35a70e54348924ddfeabf25528089d  Gtk-3.0.mipsel.typelib

The question is: why aren’t these files installed in a multiarch–aware
path? In a very old thread about gobject-introspection on -devel, Josselin
Mouette argues that adjusting paths for multiarch is not needed, but given
that we’re going through all the trouble of isolating arch–specific bits
I don’s see why not go the extra mile.

Does somebody have any suggestion, or perhaps a good rationale for the
current state of affairs?


[1] http://anonscm.debian.org/gitweb/?p=collab-maint/cattle-1.0.git;a=summary
[2] /usr/share/gobject-introspection/policy.txt
[3] http://lists.debian.org/debian-devel/2009/09/msg00958.html
Andrea Bolognani <eof@kiyuko.org>
Resistance is futile, you will be garbage collected.

Attachment: signature.asc
Description: Digital signature

Reply to: