Am Donnerstag, 29. März 2018, 15:34:05 CEST schrieb Michał Górny:
> 
> 1. Does deprecation really mean anything in terms of profiles? Even
> in the context of EAPI bans we explicitly stated that it affects new
> packages and EAPI bumps. I think deprecating it for ebuilds is still
> meaningful even if profiles would stay EAPI 5.

If we state that we deprecate *ebuilds* then it doesnt affect profiles.
So it just depends on the wording.

Having an EAPI deprecated for part of its impact is kinda messy though.

> 
> 2. Do we want to keep profiles EAPI 5 indefinitely? If we consider it
> a goal to reduce the number of EAPIs in use, I think it would be
> reasonable to bump profiles to EAPI 6 proactively, even if it doesn't
> change anything.

We can bump them, but very slowly... and best at release-like steps like 13.0 
-> 17.0. 

If your portage doesn't understand some ebuilds, that's kinda half-safe for a 
transition time (it just won't see the updates). 
If your portage doesn't understand your profile, that makes things explode 
much more efficiently.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)