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

List:       kde-frameworks-devel
Subject:    Re: kf6 vs. kf5 conflict report
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2023-03-08 15:56:15
Message-ID: CACcA1RqmQwzJgnRpdCVaPLBfUx0nP6CvtpY1c2b4z5qM_GbCYg () mail ! gmail ! com
[Download RAW message or body]

On Wed, Mar 8, 2023 at 3:13 PM Nicolas Fella <nicolas.fella@gmx.de> wrote:
>
> On 3/8/23 14:02, Harald Sitter wrote:
> > with kf6 progressing nicely here's a first conflict report of files
> > that appear in both kf6 and kf5 under the same name. this largely
> > affects translations and docs it seems. this list may not be entirely
> > comprehensive, I've only thrown together a script in a couple minutes.
>
> Thanks Harald!
>
> > one question is whether ECM should be co-installable, not sure if that
> > has been discussed
>
> It has come up, and the answer seems to be "No, it will not be
> coinstallable". This implies that ECM master will continue to support
> Qt5/KF5, but that should not be a huge burden.
>
> > report for /usr:
> > https://collaborate.kde.org/s/3gz2KfoGLsS4TF5
> >
> > furthermore the following files outside /usr clash between kf6 and 5:
> > '/etc/xdg/accept-languages.codes'
> > '/etc/xdg/kshorturifilterrc'
> > '/etc/xdg/autostart/baloo_file.desktop'
> > '/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules'
> >
> > HS

If ECM master has to support KF5, why do we have a kf5 branch? In
fact, I'm pretty sure I switched it eventually because there were
regressions.

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