I am in the process of reviewing the gxml package for sponsorship. https://salsa.debian.org/amin_modaresi/gxml One of the questions I have is about gir1.2 package naming. As I have not previously packages a gir1.2 package, I thought it best to ask here instead of making a mistake and having to do a second trip through NEW. When shipping introspection data, which can be used by packages using the GIRepository format to generate dynamic bindings, most of the packages end in what appears to be a version number. For example: gir1.2-gee-0.8 gir1.2-pango-1.0 gir1.2-secret-1 gir1.2-vte-2.91 gir1.2-wnck-3.0 However, these number do not usually correspond to the current version number of the package. gir1.2-gee-0.8 is version 0.20.8-2 gir1.2-pango-1.0 is version 1.56.3-2 gir1.2-secret-1 is version 0.21.7-2 gir1.2-vte-2.91 is version 0.82.2-1 gir1.2-wnck-3.0 is version 43.3-1 This same number (or a similar one, sometimes dropping the .0) is also included in the library package name. gir1.2-gee-0.8 is associated with libgee-0.8-2, with 2 being the SONAME. gir1.2-pango-1.0 is associated with libpango-1.0-0, with 0 being the SONAME gir1.2-secret-1 is associated with libsecret-1-0, with 0 being the SONAME gir1.2-vte-2.91 is associated with libvte-2.91-0, with 0 being the SONAME gir1.2-wnck-3.0 is associated with libwnck-3-0, with 0 being the SONAME The exception to this pattern is gir1.2-freedesktop, which does not end in a version number, and also is not associated with a library package of the same name. So, my question is, where does this number come from (and how often does it change)? Any guidance from those with more familiarity packaging GNOME software would be appreciated. P.S. I am subscribed to debian-mentors, but not debian-gtk-gnome. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.