Hello, A quick idea. Right now eclasses sometimes do API changes and start yelling at users merging ebuilds using outdates APIs. This often means users start filling bugs about outdated ebuilds requiring maintainers either to ignore that or start updating old ebuilds retroactively.
Maybe we should add some kind of devqawarn() function to eutils.eclass, which would trigger special QA warnings only when ebuild is merged by a developer? This could be triggered e.g. by some kind of voluntary make.conf setting. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
