Preparation for KF6, temporary stop of scripty on trunk/l10n-kf5

[Luigi Toscano]

Nicolas Fella ha scritto:
> Am 05.03.23 um 14:23 schrieb Luigi Toscano:
>> Karl Ove Hufthammer ha scritto:
>>> Why is kdelibs4support (with its > 3000 messages) included in the l10n-kf6
>>> branch?
>>>
>>> (And shouldn’t we have gotten rid of it a long time ago, when porting all the
>>> applications to Frameworks 5?)
>>>
>> Good question: it seems it got a kf5 branch, but the master branch is still
>> around. But its i18n settings under sysadmin/repo-metadata are using the
>> default Frameworks value, so it looks like it's master branch should be
>> tracked by trunk_kf6.
>>
>> The question then (cc-ing kde-frameworks-devel) is: should we fix the metadata
>> for the porting aids? Should we clean the master branch for those?
> 
> It makes no sense to translate the master branch for:
> 
> - kdelibs4support
> 
> - kemoticons
> 
> - kinit
> 
> - kdesignerplugin
> 
> - kdewebkit
> 
> - khtml
> 
> - kjs
> 
> - kjsembed
> 
> - kmediaplayer
> 
> - kross
> 
> - kxmlrpcclient
> 
> as they won't be released any more with KF6.
> 
>> Should we clean the master branch for those?
> 
> This has been suggested in the past, and the answer seems to be
> "probably yes".

Thank you for the confirmation. I've fixed the i18n tracking information in
the reference location (sysadmin/repo-metadata) and removed the translations
of those modules from trunk/l10n-kf6.

Ciao
-- 
Luigi