From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Fwd: [gentoo-dev] Please actively drop support for Qt5 wherever possible
Date: Thu, 2 Jan 2025 21:38:16 -0500 [thread overview]
Message-ID: <Z3dNmEIkAsbc6lIL@eversor> (raw)
In-Reply-To: <87ttahuh0s.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
On Thu, Jan 02, 2025 at 07:56:03PM +0000, Sam James wrote:
> Zoltan Puskas <zoltan@sinustrom.info> writes:
>
> >>
> >> So, removing Qt5 will break computers of many users, including my computer.
> >> In the course of many years of existence of Qt5 a large number of useful
> >> programs have been created; not all of them have been ported to Qt6. Are we
> >> going to throw away all this wealth?
> >>
> >
> > I have to agree with Andrey here, the list contains quite a few items that are
> > likely used by a lot of users and killing all these apps is going to be painful.
> >
> > Is there a timeline for killing QT5 completely or will just QT5 be stuck at the
> > current version and patch level?
> >
> > I understand that QT5 is considered deprecated, but doesn't KDE project still
> > maintain QT 5.15 for the time being? Can't we just keep that version?
> >
> > Even if we report bugs upstream, it may take time to port all these projects,
> > especially the larger ones or if they are a single person project.
>
> We best get started now then, which is the purpose of Andreas'
> email. This is the warning to start filing those bugs and asking
> upstreams to port if not done already. Not that we're going to last-rite
> such packages tomorrow.
Right, albeit can add that anything depending on qtwebengine:5 should
hurry more than the rest. As asturm already noted it's going to break
faster than the rest and nobody really wants to handle keeping that one
working. Most users also don't want two qtwebengine on their systems.
Qt5 base packages aren't the biggest worry even if we leave them
semi-abandoned (not that qtcore isn't pretty quirky and already with a
lot of small issues that will likely get worse), albeit it'd be nice to
get to a few other Qt modules out of the equation as packages ideally get
aggressively ported.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-01-03 2:38 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 [this message]
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
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=Z3dNmEIkAsbc6lIL@eversor \
--to=ionen@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