On Mon, 25 Jul 2022 16:29:28 -0300 =?UTF- 8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= <[email protected]> wrote: > Hi! > > I would really love to know why Telegram developers require so many > private headers from Qt. They shouldn't be using them at all, and if > they really require some private part they need to work with upstream > to make it public API.
This isn't only an issue for Telegram. Many projects require private headers for various reasons, because developing plugins to Qt itself is necessary to improve the system. The Qt packages have a long history of including `-private-dev` packages for the various components which provide private API that may be necessary to use in certain situations. There is no reason for that to stop happening with Qt 6.x. Especially given the upstream source is installing them during the build. The qtwayland5-private-dev package is available in Debian, and so should a qt6-wayland-private-dev package be made available containing the includes, cmake files, libraries, etc… necessary to use the QtWayland private API with Qt6.
