This portage function is stubbed in eutils and used widely within eclasses. I think we should move it to PMS.
The goal is to throw QA warnings to developers & ebuild maintainers.
Anyone opposed to adding it in EAPI 7?
This was filed in 2013 but hasn't made it into EAPI 6. So apparently there is not much interest.
It's hard to expect much attention here when it's already implemented in Portage out-of-spec.
That's a simple thing. Let's put it in EAPI=7. One function less which requires full eutils to be inherited.
(In reply to Ulrich Müller from comment #2)
> This was filed in 2013 but hasn't made it into EAPI 6. So apparently there
> is not much interest.
Well, the main reason for that was that it was implemented elsewhere.
Now, in EAPI=6 we are removing eutils.eclass whereever possible, and suddenly notice that *not* having eqawarn is kinda, dumb. So, my guess, in 2013 noone realized that side effect of EAPI=6.
Please, let's add it in EAPI=7
(In reply to Andreas K. Hüttel from comment #5)
> Please, let's add it in EAPI=7
It's on the list, see the whiteboard.
Footnote: Having this as a first-class feature would theoretically mean portage could (outside of PMS) make packages that emit eqawarn-ings fatal in some regard at a developers discretion.
The bug has been referenced in the following commit(s):
Author: Michał Górny <firstname.lastname@example.org>
AuthorDate: 2017-09-28 14:05:38 +0000
Commit: Ulrich Müller <email@example.com>
CommitDate: 2018-03-31 15:30:43 +0000
EAPI 7 has eqawarn
eapi-differences.tex | 4 ++++
pkg-mgr-commands.tex | 13 +++++++++----
2 files changed, 13 insertions(+), 4 deletions(-)}