On Tue, 2023-01-17 at 13:03 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Believe me I understand your frustration. But at the same time you > don't know the pain it takes to maintain Qt as private headers get > exposed.
Actually, I do know. I work on Ubuntu Touch, where we maintained our own Qt packages on top of Ubuntu. I've also worked on Plasma Mobile on Manjaro, which ships the KDE patch collection on Qt5, which pulled in some backported changes from Qt6, which broke ABI in the private API side, causing much frustration. Being focused on mobile, there is also the OpenGL vs GLES build issues. > Key Plasma packages are normally an exception, and Telegram desktop is > definitely not a key plasma package. And again, yes, we would love to > provide **everything**. But I sincerely do not see that happening > until someone has proper Qt maintenance as his/her day job. If the situation of Qt/KDE in Debian is as bad as you say, can we not reach out to Kubuntu/Neon devs to help out with it? Or maybe the Debian UBports Team could help, given the heavy dependence on Qt which the Lomiri stack has? I wasn't implying that telegram-desktop is a key Plasma package, however, maliit-framework and maliit-keyboard are, I would think. > That being said the plan is to switch to Plasma with Qt 6 in Trixie > (aka Debian 13), so I guess that after the freeze is over adding > Qt-Wayland's private headers will be a must. But if nothing else in Debian would require these before the freeze, why would it need to wait, since nothing would break as a result? Especially, given how anything that would require them is already broken, so not having the private headers is already an issue (hence this bug report).
