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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 45FE81382C5 for ; Mon, 8 Feb 2021 10:33:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DEA3FE08EC; Mon, 8 Feb 2021 10:33:54 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A8514E08AD for ; Mon, 8 Feb 2021 10:33:54 +0000 (UTC) Date: Mon, 8 Feb 2021 11:33:49 +0100 From: Hanno =?UTF-8?B?QsO2Y2s=?= To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GTK:2 EOL and incoming migration to GTK:3 Message-ID: <20210208113349.385f426a@computer> In-Reply-To: <20210208102221.23123.qmail@stuge.se> References: <0dce5f06-2aaf-8eea-6d76-594c112d1f7b@aisha.cc> <20210208102221.23123.qmail@stuge.se> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) 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: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 4e0cb170-8dee-4522-9441-b95d554899af X-Archives-Hash: 4938afa03984845f7a875bfab15d5dcd On Mon, 8 Feb 2021 10:22:21 +0000 Peter Stuge wrote: > "It does mean, however, that GTK 2 has reached the end of its life.=20 > We will do one final 2.x release in the coming days, and we encourage > everybody to port their GTK 2 applications to GTK 3 or 4." I read that as there will be one more gtk2 release and none after that. This seems to imply: * When there's a security flaw in gtk2 there won't be a fix from upstream. * When there's an incompatibility with new infrastructure (e.g. new gcc version / new glibc / changing API of libraries gtk depends on) there will be no updates from upstream. This means in all those instances maintainers will have to get patches from somewhere. We'll likely end up with some form of gtk-2.x-r[largenumber] with a large patchset at some point. Maintaining that will be an increasing burden. No urgency, but a sign to slowly move off gtk2. --=20 Hanno B=C3=B6ck https://hboeck.de/