public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Buschke <damage@devloop.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Fwd: [gentoo-dev] Please actively drop support for Qt5 wherever possible
Date: Thu, 2 Jan 2025 12:29:47 +0100	[thread overview]
Message-ID: <c0bc602b-758d-4d8f-8208-751fbc35906e@devloop.de> (raw)
In-Reply-To: <tagoud5sc2b7dlnyjuh6jh5p7rwcldqrh7nroxkh3bof5clr5d@2x7bwd25t5ud>



Am 02.01.25 um 12:13 schrieb Zoltan Puskas:
>>
>> 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?
>>
> 
> Is there a timeline for killing QT5 completely or will just QT5 be stuck at the
> current version and patch level?

That's what I thought first, too. And I think that is the question which 
has to be answered before making a decision. As long as someone, who 
could be referred to as upstream, patches QT5, I would personally be 
fine with using QT5. But once that support drops, we are talking about 
an unsupported biiiiig piece of software which you don't want to have on 
your computer.

I searched the web and found a blog entry [1] talking about extended 
commercial(!) support ending mid 2025. But I don't know QT enough to 
qualify this information.

regards
Daniel


[1] 
https://www.qt.io/blog/qt-5.15-extended-support-for-subscription-license-holders


  parent reply	other threads:[~2025-01-02 11:29 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 [this message]
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
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=c0bc602b-758d-4d8f-8208-751fbc35906e@devloop.de \
    --to=damage@devloop.de \
    --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