From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8ABDA15812D for ; Fri, 03 Jan 2025 02:38:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A7F1CE08BE; Fri, 03 Jan 2025 02:38:20 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3207EE08AD for ; Fri, 03 Jan 2025 02:38:20 +0000 (UTC) Date: Thu, 2 Jan 2025 21:38:16 -0500 From: Ionen Wolkens To: gentoo-dev@lists.gentoo.org Subject: Re: Fwd: [gentoo-dev] Please actively drop support for Qt5 wherever possible Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <3346777.aeNJFYEL58@tuxbrain.fritz.box> <87ttahuh0s.fsf@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Bw8CQxpbkU4DFVLV" Content-Disposition: inline In-Reply-To: <87ttahuh0s.fsf@gentoo.org> X-Archives-Salt: 23bebd80-9fa1-4518-9ec8-230a6d8b3bdc X-Archives-Hash: 0f8d6fddbb4b1342680b56be723b8363 --Bw8CQxpbkU4DFVLV Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 02, 2025 at 07:56:03PM +0000, Sam James wrote: > Zoltan Puskas writes: >=20 > >>=20 > >> So, removing Qt5 will break computers of many users, including my comp= uter. > >> In the course of many years of existence of Qt5 a large number of usef= ul > >> programs have been created; not all of them have been ported to Qt6. A= re we > >> going to throw away all this wealth? > >>=20 > > > > I have to agree with Andrey here, the list contains quite a few items t= hat 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 stuc= k 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 pro= jects, > > especially the larger ones or if they are a single person project. >=20 > 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. --=20 ionen --Bw8CQxpbkU4DFVLV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmd3TZgACgkQskQGsLCs QzQgXggArq+QN+Acsf6gD3h9ZmjU21L7iwunNB4XOQDbltdo6ECYWheF27iut6dk FHhu9veugZN55RktFbsYHFq38mbu3BqqG0MoJxXrAajv4XEPFVmAw9eVFqDi1FbP 6+uu1DfT1wWqUl3qyC37RxE84qPghgu0k0yQYf6RPZEICv+JKLczFUkDc3lN5khY SD/JjnjGIrR1EucYTSfr/F6pWKOZ0h14PrQO2GYYr+HZ4ZuiLn2ZEBh0NS4RFp1X kQC5RBhqM07oH6LVywhlWhDiC8zp4PIMuhkudHzgQuu8aFEvQQ1ySM58K1jzG7Hx 1mFFSg411Jf/AIFP6rH2XZjERXSrAQ== =0xf+ -----END PGP SIGNATURE----- --Bw8CQxpbkU4DFVLV--