[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: kio-extras and the KF5/KF6 period
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2023-06-07 11:00:13
Message-ID: 0c8ae0cb-ab3a-cbbc-6ab3-2b50585ee4dd () tiscali ! it
[Download RAW message or body]

David Redondo ha scritto:
> Am Donnerstag, 25. Mai 2023, 12:51:32 CEST schrieb Nicolas Fella:
>> Hi,
>>
>> Am 17.05.23 um 00:02 schrieb Albert Astals Cid:
>>> kio-extras provides plugins for kio.
>>>
>>> So KF5 applications want a KF5 kio-extras and KF6 applications want a KF6
>>> kio- extras.
>>
>> This is also the case in more places, e.g. Breeze/Oxygen and
>> plasma-integration, so having a unified approach would make sense.
>>
>>> If we're going to support a period on which we ship both Kf5 and KF6 based
>>> applications we need to:
>>>
>>> Make sure kf5 and kf6 are coinstallable.
>>>
>>> a) release two tarballs, one for each KF
>>
>> In some cases, where there is a large enough divergence between the 5
>> and 6 code we might want to have separate branches to maintain those
>> (e.g. master is Qt6 and we have a qt5-compat branch).
>>
> 
> I think plasma-integration is already at that point where it's very hard to 
> maintain and do something because it's becoming a soup of #ifdefs.
> Checking 5 vs. 6 but also checking Qt6 Patch levels which is only going to 
> become worse in the future. For exmaple if we want to use  QNativeInterface 
> API which theoretically would  make the code easier to read or dbus menu 
> support which might end up needing to do different thing depending on the Qt 6
> version.
> 
> So for plasma-integration I would like to no longer have 5 and 6 support in 
> master.

I think this is a different case: plasma-integration is part of plasma, and
afaik the maser branch of all repositories which are part of plasma are
Qt6-only already.

-- 
Luigi
[prev in list] [next in list] [prev in thread] [next in thread]