From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Fwd: [gentoo-dev] Please actively drop support for Qt5 wherever possible
Date: Thu, 02 Jan 2025 19:58:31 +0100 [thread overview]
Message-ID: <3355554.aeNJFYEL58@tuxbrain.fritz.box> (raw)
In-Reply-To: <ur05ligz8@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
On Donnerstag, 2. Jänner 2025 12:37:47 Mitteleuropäische Normalzeit Ulrich
Müller wrote:
> Can you provide a pointer to a Qt upstream page saying that Qt 5 is
> deprecated? Just for the case that the upstreams of my packages need
> further convincing.
Not sure I can, without accompanying explanations:
https://www.qt.io/blog/qt-offering-changes-2020
Qt5 upstream (Qt Company) OSS support ended on 2020-12-08. Since then, bugs
are only fixed if reproduced in Qt6 first, then backported. Since then, public
availability of commercial 5.15 LTS releases is delayed by 1 year, including
repository access for cherry-picking - this is important, see below, and
affects Gentoo first and foremost.
The last official LTS release will be this April/May:
https://www.qt.io/blog/qt-5.15-extended-support-for-subscription-license-holders
https://wiki.qt.io/Qt_5.15_Release#Release_Plan
Public availability of this release will be *1 year later*. Some may think
now, fine, updates (3 in total) until 2026! However, if a dependency/toolchain
upgrade down the stack breaks Qt5 between now and March/April, to be then
fixed in their final release, you will be waiting until April/May 2026 for
that to be available. If it breaks later than April 2025, you will be waiting
forever. In either case, you rely on downstream volunteer patchwork.
KDE Qt5PatchCollection ultimately relies on Qt company's upstream commits as
well, so don't expect any original work from there to get things fixed. In any
case, there is no clear EOL date for these patches, but they *will* be drying
up as there is no main KDE consumer left, I certainly know that my
contributions come to an end.
https://community.kde.org/
Qt5PatchCollection#For_how_long_will_this_be_maintained?
Gentoo Qt Policy page:
https://wiki.gentoo.org/index.php?title=Project:Qt/
Policies#Handling_different_versions_of_Qt
Gentoo Qt migration notes:
https://wiki.gentoo.org/wiki/Project:Qt/Qt6_migration_notes
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 789 bytes --]
next prev parent reply other threads:[~2025-01-02 18:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 21:50 Fwd: [gentoo-dev] Please actively drop support for Qt5 wherever possible Andreas Sturmlechner
2025-01-02 6:36 ` Andrey Grozin
2025-01-02 11:13 ` Zoltan Puskas
2025-01-02 11:22 ` James Le Cuirot
2025-01-02 11:29 ` Alexey Sokolov
2025-01-02 18:57 ` Andreas Sturmlechner
2025-01-02 18:57 ` Andreas Sturmlechner
2025-01-02 19:03 ` Philip Webb
2025-01-02 19:05 ` Andreas Sturmlechner
2025-01-02 11:29 ` Daniel Buschke
2025-01-02 12:22 ` Viorel Munteanu
2025-01-02 18:47 ` Andreas Sturmlechner
2025-01-02 19:56 ` Sam James
2025-01-03 2:38 ` Ionen Wolkens
2025-01-03 13:41 ` Andreas Sturmlechner
2025-01-02 11:19 ` Lucio Sauer
2025-01-02 19:39 ` Eli Schwartz
2025-01-02 19:51 ` Sam James
2025-01-02 11:37 ` Ulrich Müller
2025-01-02 18:58 ` Andreas Sturmlechner [this message]
2025-01-28 20:53 ` Andreas Sturmlechner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3355554.aeNJFYEL58@tuxbrain.fritz.box \
--to=asturm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox