Is Avahi Qt 5 main loop glue desirable?
avahi 0.8, which is currently being packaged, adds Qt 5 main loop glue
(avahi-qt5.pc) in addition to its old Qt 4 and Qt 3 support (which has
been disabled in Debian since 2017).
The initial upload will probably leave the Qt 5 support disabled, because
members of the Utopia team are more familiar with the C/GLib ecosystem,
and enabling it would require a trip through NEW. However, avahi will
have to go through NEW at some point anyway, to switch from Python 2
to Python 3.
Is Qt 5 main loop glue for Avahi something that the Qt/KDE team expect
to need?
If so, is there anyone in the Qt/KDE team who could add themselves to
Avahi's Uploaders and make sure the Qt parts keep working as intended?
(Because Qt in Debian has GLib main loop integration enabled, Qt
applications could equally well rely on libavahi-glib-dev and
avahi_glib_poll_get(), if that's preferred; or they could use the
built-in avahi_threaded_poll_get() to do their Avahi processing in
another thread, or implement their own main loop integration.)
Thanks,
smcv
Reply to: