Hi, On Tue, 17 Jan 2023 at 13:32, Rodney Dawes <dobey.p...@gmail.com> wrote: > > 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.
You do definitely know the landscape then :) > > 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? The main Qt 5 maintainer is also Ubuntu's maintainer. From time to time people from Ubuntu try to help us, with various degrees of success, and here we are. Note that we do stress a lot what we think a Debian package should be, and sometimes that clashes with other distros expectations (and that's fine!). > I wasn't implying that telegram-desktop is a key > Plasma package, however, maliit-framework and maliit-keyboard are, I > would think. Yes, but still not using Qt 6, so no need on our side to create more work for us while not yet there. It would be much much easier if they just used _stable_ API. And that's where we get back to upstream, plugins, etc. Create _stable_ API and everything goes smooth. > > 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? No *key* package. As soon as we add private headers we gain non-key packages trying to use them, and thus more man power at the time of updating Qt. > 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). No, see above. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/
