Re: Qt5->Qt6 transition chaos for packagers when depending applications are not yet ported.

Ben Cooksley <[email protected]> Thu, 5 Oct 2023 03:01:30 +1300
Newsgroups gmane.comp.kde.devel.general,gmane.comp.kde.devel.pim
Message-ID <CA+XidOGsyJDyE88La=o-LtyoK2eJ0WtNFGKDLOvhj-W3Mx4oNA@mail.gmail.com>
On Thu, Oct 5, 2023 at 2:16 AM Scarlett Moore <
[email protected]> wrote:

> Hello everyone!
> Obviously we expect there to be bumps in the road while packaging
> unstable ( master ), however in most cases you can set
> QT_VERSION_MAJOR and dual build qt5 and qt6 version to satisfy both
> qt5 and qt6 applications. I have stumbled on libkgapi which master
> does not support this and will only build qt6. kio-gdrive is not yet
> ported and as such creating a bit of chaos with apt. We have come up
> with a workaround, but shouldn't libraries still support both when
> there are applications out there that still depend on the qt5 variant?
>

Just as a side note here - where this happens, the CI system should begin
to alert people as it will no longer be able to locate the dependency in
question.

From my perspective though, leaves (applications) should move before any
branches (libraries) move.


> Thanks,
> Scarlett
>

Cheers,
Ben