>>>>> On Mon, 02 Mar 2020, Michał Górny wrote:

> Not sure if this is practically able but technically I see an advantage
> from having three distinct states:

> 1. Deprecation -- tooling warns about them but there are no consequences
> for adding new ebuilds.

> 2. Ban I -- tooling errors out, if developers add new ebuilds
> (as in real new ebuilds), we pursue it.

Does this really occur at a scale that should bother us? The main
blocker for removal of old EAPIs are unmaintained ebuilds, and for
these any levels of more fine-grained bans won't help.

> 3. Ban II -- no ebuilds left, CI fatal, immediate revert.

Ulrich