<div id="__MailbirdStyleContent" style="font-size: 8pt;font-family: Arial;color: #000000">
I agree let's move ahead. We can't be defined by what Jolla does and needs<div><br></div><div>However let's only do it if development is going to pick up. No need to annoy Jolla and then for everything to stall.<br><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">On 10/02/2021 20.39.59, Carl Schwan <carl@carlschwan.eu> wrote:</p><div style="font-family:Arial,Helvetica,sans-serif">Le mercredi, février 10, 2021 7:45 PM, Pierre <pinaraf@pinaraf.info> a écrit :
<br>
<br>> On Wednesday, February 10, 2021 9:30:43 AM CET Adam Pigg wrote:
<br>>
<br>> > I wish!!! ... try qt 5.6!
<br>> > On Wed, 10 Feb 2021 at 08:14, Halla Rempt boud@valdyas.org wrote:
<br>> >
<br>> > > On Wednesday, 10 February 2021 08:44:54 CET Pierre wrote:
<br>> > >
<br>> > > > Is there a lot of people still trying to build Calligra with Qt 5.3 or
<br>> > > > KF5
<br>> > > > 5.7.0 ? These are years old, and I guess building Calligra with them has
<br>> > > > been untested for some time.
<br>> > >
<br>> > > I think that the Jolla people still build the documents application with
<br>> > > Qt 5.9.
<br>> > > --
<br>> > > https://www.krita.org
<br>>
<br>> I created this MR then :
<br>> https://invent.kde.org/office/calligra/-/merge_requests/10
<br>>
<br>> At least it's no longer Qt 5.3 / KF 5.7, and a bunch of deprecated stuff is
<br>> cleaned up (I built locally disabling deprecated Qt APIs).
<br>>
<br>> But Jolla decided to stay at Qt 5.6 out of fear from LGPLv3, as far as I
<br>> understand. Does it means Calligra would have to be stuck in an untested
<br>> setup? I no longer have a Jolla phone, do they update from Calligra
<br>> frequently? And is there a lot of people still building with Qt 5.6 and
<br>> testing so we are sure there is no regressions there?
<br>
<br>Hi,
<br>
<br>Your MR looks good to me. Concerning the minimum version requirement, I worked
<br>a bit last year to remove a lot of warnings and I was blocked to move further
<br>by the minimum requirements.
<br>
<br>Personally, I'm not sure if it is worth continuing to support Qt 5.6. Calligra can't
<br>continue to use on Qt 5.6 as the minimum required version for years when we are
<br>moving to Qt 6 in a timespan of 1 or 2 years with the rest of KDE. Also as
<br>you said I'm not sure anyone is testing regressions and the Gemini QML code
<br>is definitively using Qt 5.12 only code. Jolla needs to move forwards with their
<br>LGPLv3 problem or they will end up obsolete compared to the rest of the Qt world.
<br>
<br>I would propose moving all the way to Qt 5.12 or even 5.15, so we can start
<br>fixing deprecations in time for Qt6. And maybe in the second step, we should
<br>consider moving to C++17 too.
<br>
<br>Regards,
<br>Carl
<br>
<br>
<br></pinaraf@pinaraf.info></div></blockquote>
</div></div>