kio-fuse and Qt6/KF6 - Was: Re: Upcoming CI changes - transition to VM based CI

[Stefan Brüns]

On Dienstag, 10. Juni 2025 09:28:45 Mitteleuropäische Sommerzeit Ben Cooksley 
wrote:
> On Mon, Jun 9, 2025 at 8:55 PM Stefan Brüns <stefan.bruens at rwth-aachen.de>
> 
> wrote:
> > On Dienstag, 3. Juni 2025 17:38:54 Mitteleuropäische Sommerzeit Volker
> > Krause
> > 
> > wrote:
> > > On Montag, 2. Juni 2025 16:42:01 Mitteleuropäische Sommerzeit Christoph
> > > 
> > > Cullmann wrote:
> > > > Have we some overview how many things on invent.kde.org will loose
> > 
> > the the
> > 
> > > > CI as they are still Qt 5 only?
> > >
> > >...
> > >
> > > * KF5 and other libraries supporting any of the above.
> > 
> > I think the big elephant in the room is kio-fuse. The Qt6 version is still
> > broken [1][2], so the "backend" has to use the Qt5 version even for
> > installations where everything else has migrated to Qt6.
> 
> That seems like more of a distribution issue than a CI issue though?
> 
> The CI system does not allow for multiple Qt versions to be present.

No, it is not a distribution issue. When you install a Qt6 based kio-fuse, you 
have a broken kio-fuse.

Kio-fuse can only be installed using one version on a system, *either* Qt5 
based *or* Qt6 based. It does not matter what Qt/KF version the session is 
using, dispatching happens at run time. You could use kio-fuse-5 with a KF6 
plasma session, kio-fuse-6 with KF5, kio-fuse-5 with KF5, and kio-fuse-6 with 
KF5. But anything using kio-fuse-6 is broken.

If you want a correctly working kio-fuse in a KF6 session, you *have to* 
provide Qt5 and Qt6 on the system, at least the runtime libraries. (You can of 
course build both separately, and have the headers etc. present only in one 
version.)

Regards,

Stefan

-- 
Stefan Brüns  /  Bergstraße 21  /  52062 Aachen
phone: +49 241 53809034     mobile: +49 151 50412019
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20250610/0d3514cc/attachment.sig>