Those of you who write #linux#apps which interface with #dbus, especially in the context of #gtk, what are your strategies for managing dbus interface versioning for services.
Easiest thing to do is just grab the latest .xml dbus interface definitions and codegen clients. However, there are versioning implications with this, as the client maybe outdated depending on the distro your app runs on. Is there a common practice around handling this in the community?
Any sane developer would see this kind of repetition and go "hold on, maybe we're overcomplicating this":
Dbus service name: org.freedesktop.resolve1
Dbus object path: /org/freedesktop/resolve1 Dbus interface name and method: org.freedesktop.resolve1.Manager.ResolveHostname
All for one simple method call. This pattern repeats over and over and over for Dbus services.
I can't decide if it's the result lack of thinking through options or sadism.
xdg-desktop-portal should be documented separately from flatpak.
I profoundly dislike flatpak among other reasons because of its sense of #FalseSecurity (sandboxes still run on the same kernel, I might withdraw this objection when they start using #gVisor for everything) and also because of the vendoring (https://wiki.gentoo.org/wiki/Why_not_bundle_dependencies) it encourages, but I can also recognize that for other reasons that #dBus interface is a good idea.