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