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 731E41382C5 for ; Tue, 6 Mar 2018 01:53:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0932FE0864; Tue, 6 Mar 2018 01:53:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 A5D48E0856 for ; Tue, 6 Mar 2018 01:53:18 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id CB9D5335C36 for ; Tue, 6 Mar 2018 01:53:16 +0000 (UTC) Received: by mail-io0-f178.google.com with SMTP id v6so20235241iog.7 for ; Mon, 05 Mar 2018 17:53:16 -0800 (PST) X-Gm-Message-State: AElRT7FH72FbCLL2+MgeqRFzH/eGy9j44UzeWvLoF7/m9ffa08WY0eq3 aW1Faq1wmXRRkq2bI5xs75+8uBPjc+XJ9OYrAHU= X-Google-Smtp-Source: AG47ELvgVTppVGH0aQ0LSE0tx5puvWPYUH1ZYV43pt5tiEkr8wKa6lneHL7XaOoXKhsvi+DGzKJJHz6N5l5ZtCIlvL0= X-Received: by 10.107.180.196 with SMTP id d187mr20028486iof.187.1520301194925; Mon, 05 Mar 2018 17:53:14 -0800 (PST) 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 MIME-Version: 1.0 Received: by 10.2.168.15 with HTTP; Mon, 5 Mar 2018 17:52:54 -0800 (PST) From: Matt Turner Date: Mon, 5 Mar 2018 17:52:54 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: [gentoo-dev] Is removing old EAPIs worth the churn? To: gentoo development Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 65c58a92-9c61-4f9f-8ea3-0cd2b8dbeffc X-Archives-Hash: a7150359cd37c2ede079924550790c75 EAPI 2 removal bug: https://bugs.gentoo.org/648050 It seems like tons of churn to update old stable ebuilds to a new EAPI, just for its own sake. Take https://bugs.gentoo.org/648154 for example. New ebuild added with EAPI 6 bumped from EAPI 2. Otherwise functionally identical. Now asking arch teams to retest and restabilize. Multiply by 100 or more. In the end we might get to delete some code from portage or an eclass? Does this seem worth it?