From: Aaron Bauman <bman@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2021-07-11 - call for agenda items
Date: Mon, 5 Jul 2021 17:19:32 -0400 [thread overview]
Message-ID: <YON3ZDsxZ6OL26MS@Aaron-Baumans-MacBook-Pro.local> (raw)
In-Reply-To: <uk0m512v4@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Mon, Jul 05, 2021 at 12:17:35PM +0200, Ulrich Mueller wrote:
> >>>>> On Mon, 05 Jul 2021, Ulrich Mueller wrote:
>
<snip>
> In the past, the council had also banned EAPIs. However, that didn't
> make much of a practical difference because an EAPI cannot be added
> to eapis-banned in layout.conf unless all ebuilds are gone. Maybe we
> should have a rule like the following instead:
> "A deprecated EAPI is considered banned when the Gentoo repository
> no longer contains any ebuilds using it."
Having the council vote to officially ban an EAPI does have
practicality. The work done by those porting ebuilds, removing old
packages, etc is hindered when other begin committing ebuilds deprecated
but not banned.
I would ask that the council continue the official motions and votes to
ban EAPI's prior to being "enforced" by tooling. This assists those doing
the work and the QA team to stop people from committing.
While it is an administrative control it does help, but a technical
solution would be preferred long term.
-Aaron
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-05 21:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 9:20 [gentoo-project] Council meeting 2021-07-11 - call for agenda items Ulrich Mueller
2021-07-05 10:17 ` Ulrich Mueller
2021-07-05 10:19 ` Ulrich Mueller
2021-07-05 21:19 ` Aaron Bauman [this message]
2021-07-05 21:42 ` Ulrich Mueller
2021-07-05 21:53 ` Aaron Bauman
2021-07-06 7:02 ` Ulrich Mueller
2021-07-06 13:59 ` Thomas Deutschmann
2021-07-06 15:40 ` Ulrich Mueller
2021-07-06 17:42 ` Aaron Bauman
2021-07-06 17:55 ` Ulrich Mueller
2021-07-06 19:32 ` Rich Freeman
2021-07-07 13:45 ` Michał Górny
2021-07-07 1:59 ` Rich Freeman
2021-07-07 6:55 ` Sam Jorna (wraeth)
2021-07-07 11:25 ` Rich Freeman
2021-07-07 13:00 ` Sam Jorna (wraeth)
2021-07-07 11:40 ` Joonas Niilola
2021-07-07 11:51 ` Rich Freeman
2021-07-07 11:57 ` Ben Kohler
2021-07-07 13:41 ` Michał Górny
2021-07-07 20:38 ` Robin H. Johnson
2021-07-07 5:08 ` Robin H. Johnson
2021-07-07 9:27 ` Ulrich Mueller
2021-07-07 11:31 ` Rich Freeman
2021-07-07 20:28 ` Robin H. Johnson
2021-07-07 21:24 ` Rich Freeman
2021-07-08 16:57 ` Robin H. Johnson
2021-07-08 17:43 ` Ulrich Mueller
2021-07-08 17:51 ` Robin H. Johnson
2021-07-25 17:22 ` Ulrich Mueller
2021-07-08 17:43 ` Rich Freeman
2021-07-07 20:23 ` Robin H. Johnson
2021-07-07 23:00 ` Ulrich Mueller
2021-07-08 16:58 ` Robin H. Johnson
2021-07-08 15:44 ` [gentoo-project] Council meeting 2021-07-11 - agenda Ulrich Mueller
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=YON3ZDsxZ6OL26MS@Aaron-Baumans-MacBook-Pro.local \
--to=bman@gentoo.org \
--cc=gentoo-project@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