From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Is removing old EAPIs worth the churn?
Date: Tue, 6 Mar 2018 15:39:13 -0800 [thread overview]
Message-ID: <CAEdQ38F6=vpVrpe9tnb9L1j=mBz6k6xbt9F18A_mi9MqSE9bGw@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr_dpupaOgS0WJFi8oUFNqGaW6QkG2H7DxN=rr-S9BCi3w@mail.gmail.com>
On Tue, Mar 6, 2018 at 2:27 PM, Alec Warner <antarus@gentoo.org> wrote:
> On Tue, Mar 6, 2018 at 5:22 PM, Matt Turner <mattst88@gentoo.org> wrote:
>> On Tue, Mar 6, 2018 at 1:35 PM, Rich Freeman <rich0@gentoo.org> wrote:
>> > On Tue, Mar 6, 2018 at 4:17 PM, Andreas K. Huettel
>> > <dilfridge@gentoo.org> wrote:
>> >>
>> >> Is it worth the effort? Yes, see below.
>> >> Is it a high priority task? No.
>> >>
>> >
>> > It sounds like all that has been done is to log a tracker and create
>> > some bugs. That is hardly a major burden on anybody. If it nudges
>> > people to bump the EAPI when they're doing other work so much the
>> > better, but there doesn't seem to be a drop-dead date yet.
>> >
>> > If devs don't want to think about EAPI cleanup they don't have to right
>> > now.
>>
>> No, not true. Look at the blocking bugs. We're asking arch teams to
>> retest and restabilize ebuilds whose only difference is the EAPI bump.
>>
>
> Ultimate the arch teams are supposed to test the ebuild (that it works), so
> when we change the EAPI of the ebuild re-testing is required.
Of course, but that's not the point...
next prev parent reply other threads:[~2018-03-06 23:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 1:52 [gentoo-dev] Is removing old EAPIs worth the churn? Matt Turner
2018-03-06 5:56 ` Kent Fredric
2018-03-06 22:11 ` Matt Turner
2018-03-06 9:00 ` Dirkjan Ochtman
2018-03-06 22:13 ` Matt Turner
2018-03-10 5:07 ` Kent Fredric
2018-03-06 13:53 ` Michał Górny
2018-03-06 21:17 ` Andreas K. Huettel
2018-03-06 21:35 ` Rich Freeman
2018-03-06 22:22 ` Matt Turner
2018-03-06 22:27 ` Alec Warner
2018-03-06 23:39 ` Matt Turner [this message]
2018-03-07 0:12 ` Rich Freeman
2018-03-06 22:21 ` Matt Turner
2018-03-07 0:48 ` Andreas K. Huettel
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='CAEdQ38F6=vpVrpe9tnb9L1j=mBz6k6xbt9F18A_mi9MqSE9bGw@mail.gmail.com' \
--to=mattst88@gentoo.org \
--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