On Sat, 12 Oct 2024 at 07:58:00 +0200, Andreas Tille wrote:
Hi Simon,

If you want a message to reach the submitter of a bug report, please remember to Cc them - I didn't see your replies to this bug report until I happened to see them in the BTS web interface now, because I am not a maintainer of the kbdd package.

I'm about to do an ITS upload of kbdd[1] and I would love to support
your attempt to minimize the dbus-glib usage.  However, if I simply drop
the libdbus-glib-1-dev Build-Depends this line[2] fails the configure
step.

([1] and [2] were broken links, but at the time of writing, https://sources.debian.org/src/kbdd/0.7.1-1/configure.ac#L45 works as a replacement reference for [2].)

On Sat, 12 Oct 2024 at 14:48:51 +0200, Andreas Tille wrote:
after our conversation I dived deeper into this, deactivated
the test in configure.ac which lead to

 dbus-binding-tool: command not found

which makes me assume that

 libdbus-glib-1-dev-bin: /usr/bin/dbus-binding-tool

is needed.  So it seems this bug can't be fixed easily and I
leave it untouched.

Yes, if kbdd is written to use dbus-glib then it will require porting to be able to avoid dbus-glib without dropping features.

If the feature "Enable providing D-BUS object" is not particularly important, then this package could probably be configured with --disable-dbus. I have no idea what this package is or what it does, so I can't judge whether its D-Bus-related features are essential, unnecessary, or anything in between.

Otherwise, it will need changes to the C code and build system, which would be something to be done upstream. Uusually the most appropriate replacement for dbus-glib is GLib's GDBus, for which there is a porting guide at <https://docs.gtk.org/gio/migrating-gdbus.html>. Practical examples of porting from dbus-glib to GDBus can be found in the VCS history of many older GNOME projects.

Note that kbdd appears to be dead upstream (https://github.com/qnikst/kbdd/issues/52) so any porting would likely have to be done by someone who is also willing to become the new upstream maintainer.

    smcv

Reply via email to