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