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 AF5801382C5 for ; Tue, 6 Mar 2018 22:13:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2DB21E0A07; Tue, 6 Mar 2018 22:13:35 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.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 D2CB4E0973 for ; Tue, 6 Mar 2018 22:13:34 +0000 (UTC) Received: from mail-io0-f171.google.com (mail-io0-f171.google.com [209.85.223.171]) (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 97040335C2C for ; Tue, 6 Mar 2018 22:13:33 +0000 (UTC) Received: by mail-io0-f171.google.com with SMTP id d71so739831iog.4 for ; Tue, 06 Mar 2018 14:13:33 -0800 (PST) X-Gm-Message-State: APf1xPCKY+GwNpK9r5q9ZTv+BA5Gg/0r5n57aJ3pBGwU4uhFRTREiORp sHXCvkxWabelHKk9cqsuEZRa1JDmmzrDOEZ4UGc= X-Google-Smtp-Source: AG47ELs5+SthSjuiFlgKv7amWWx96arWn7qmWBkYOzSVHNJgCAkp20JH52VimktNZ5NoDFipQPTPvRBQLW8llrSm1ZY= X-Received: by 10.107.212.7 with SMTP id l7mr22653182iog.70.1520374411899; Tue, 06 Mar 2018 14:13:31 -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; Tue, 6 Mar 2018 14:13:11 -0800 (PST) In-Reply-To: References: From: Matt Turner Date: Tue, 6 Mar 2018 14:13:11 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-dev] Is removing old EAPIs worth the churn? To: gentoo development Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 77600741-a27a-483e-ab14-aad53967a18a X-Archives-Hash: 3609f248b63a8bf5dabc52dbc3e7fec9 On Tue, Mar 6, 2018 at 1:00 AM, Dirkjan Ochtman wrote: > On Tue, Mar 6, 2018 at 2:52 AM, Matt Turner wrote: >> >> In the end we might get to delete some code from portage or an eclass? >> Does this seem worth it? > > > To add to some of the points Kent made, I think so, yes: this means freeing > us from the cognitive overhead of thinking about older EAPIs at all, having > to remember the differences between those old EAPIs and the newer ones. > Removing that complexity from developer's minds as well as from our tooling > means our tooling will be we can spend our time and energy on other things, > which will be a win for the distribution. > > Yes, the long tail is painful: these are probably the packages that haven't > been upgraded before for a reason, but actually putting the finishing > touches on the EAPI migration will be worth it in the end. The long tail of packages were packages that by definition didn't require any maintenance or add to our collective cognitive overhead. :)