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