GNOME Bugzilla – Bug 773197
Remove libsoup-2.4 bindings
Last modified: 2018-05-22 15:40:15 UTC
As discussed in bug #773177c#7, consider removing libsoup-2.4.vapi. It's very confusing to have bindings distributed by vala that are not actually ever used.
libsoup has been distributing bindings for several years so it should be safe to remove the ones shipped with Vala. libsoup isn't alone; we also do this for (at least) gedit, gnome-keyring-1, gtksourceview3, libgdata, librsvg2, and packagekit-glib2. Does anyone have a compelling reason not do this? It seems okay to me…
You should do the same for libgda, it has bindings too since 4.0 and know with recent 5.2 version. Vala distribute an outdated 4.0 version.
Does libgda not build the Vala bindings by default? The libgda-devel RPM for FC24 (at least) doesn't include a VAPI, so removing libgda from Vala probably isn't safe. All the packages I listed above have VAPIs in their Fedora packaging; we should probably check Debian, too, before we remove anything. Meanwhile, libgda-devel not including a VAPI sounds like a packaging bug.
Debian seems to be in the same situation regarding libgda; the only package with a libgda-4.0.vapi is valac, and no packages have a libgda-5.0.vapi. IMO libgda-4.0.vapi should stay.
(In reply to Evan Nemerson from comment #4) > Debian seems to be in the same situation regarding libgda; the only package > with a libgda-4.0.vapi is valac, and no packages have a libgda-5.0.vapi. > IMO libgda-4.0.vapi should stay. This is a bug on both RPM and Debian. Libgda requires to enable Vala bindings by using a set of switches like --enable-gi-gda --enable-vala Even the is a GDA data library written by me in Vala in GDA, may no body knows because it requires to enable Vala and Introspection. Do you need to GDA enables this features by default? I can do it as the maintainer of GDA Vala bindings. Just file a bug.
(In reply to Evan Nemerson from comment #4) > Debian seems to be in the same situation regarding libgda; the only package > with a libgda-4.0.vapi is valac, and no packages have a libgda-5.0.vapi. > IMO libgda-4.0.vapi should stay. GDA 4.0 is not maintained and Debian and Fedora, may no buddy, ship that version, then should be removed as it is unusable, because API break on GDA 5
(In reply to Daniel Espinosa from comment #5) > This is a bug on both RPM and Debian. Libgda requires to enable Vala > bindings by using a set of switches like --enable-gi-gda --enable-vala I don't think we would have any interest using such a configure flag in Fedora anyway. We would wind up with a different set of Vala bindings than other distributions using the default configure flags, which would be a horrible compatibility problem. > Do you need to GDA enables this features by default? I can do it as the > maintainer of GDA Vala bindings. Just file a bug. If you want the bindings to be used, then yes.
Ok. I'll work on and file a bug. May you want to rename this Bug's title to"Remove unnecessary bindings" or so, then make depends on file d bugs for each library with Vala bindings support upstream.
libsoup Vala bindings were added upstream 7 July 2015: https://git.gnome.org/browse/libsoup/commit/?id=519c6695fc78b2e2c86c75328d24cbb6d605d132
Is anything holding up the removal or can I "just do it"?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vala/issues/561.