On Tue, 2023-01-17 at 13:43 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> 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,
And to add to the point, currently the qt6-wayland package is broken in
Debian, even just trying to find it via CMake, because some of these
files have been removed. The following error is from simply checking
for the WaylandClient Qt component via:
find_package(Qt6 6.2 REQUIRED COMPONENTS Core Wa
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
ow
On Mon, 2023-01-16 at 23:35 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Maintaining Qt already takes a lot of time, adding private headers
> only makes things worse. So if you want to do porting and the headers
> are not yet there you will have to build Qt itself or fix the problem
> where
On Mon, 2023-01-16 at 21:35 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Hi
>
> Private packages have only been created when required for other Qt
> submodules or key plasma packages, no more.
They are required for key plasma packages here, as well. It is
necessary to use these private hea
On Mon, 25 Jul 2022 16:29:28 -0300 =?UTF-
8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?=
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 ne
6 matches
Mail list logo
