> But I'm wondering, is there any usage for maliit-server-qt5 without > maliit-inputcontext-qt5 ?
I am making this change now. One reason to not universally depend on maliit-inputcontext-qt5 is that qt5 has reached End of Life and some people may want to have a system without qt5 installed. I agree that if someone has maliit-server-qt5 installed, then that concern doesn't matter. I don't think this minor packaging change helps with your bigger issue though. maliit-inputcontext-qt5 is needed for you to use Maliit as intended with qt5 apps. Debian Lomiri Unstable now uses maliit qt6 which proves that it is possible to have a system without maliit-server-qt5 now. If Mobian needs to have maliit-inputcontext-qt5. then I recommend that you update the Mobian metapackage to depend on it. Similarly, there are an increasing number of qt6 apps now, so you want support for qt6 also. By the way, there is an interesting packaging trick we use for ibus-gtk3 to avoid a direct dependency on gtk3. It's in the override_dhslibdeps part of https://salsa.debian.org/debian/ibus/-/blob/master/debian/rules . In that case, it's as simple as removing a single automatic dependency, libgtk-3-0t64. It's awkward to use that technique for maliit-inputcontext-qt5 since qt5 is split into many different binary packages. I guess we could do it though. Then we could simply depend on both maliit-inputcontext-qt5 and maliit-inputcontext-qt6 without requiring qt5 to be installed where it isn't wanted. Thank you, Jeremy Bícha
