| 1 |
On Wed, 11 Jun 2008 09:18:07 +0200 |
| 2 |
Luca Barbato <lu_zero@g.o> wrote: |
| 3 |
> Ciaran McCreesh wrote: |
| 4 |
> > Ok, if EAPI 2 turns on src_test except where explicitly overridden |
| 5 |
> > by the ebuild, explain how EAPI 2 src_test failures are meaningless |
| 6 |
> > in the same way that EAPI 0/1 src_test failures are. |
| 7 |
> |
| 8 |
> Test failures aren't meaningless right now. Applications with good |
| 9 |
> test suites got them used by the people that cares already. |
| 10 |
|
| 11 |
The point you've been missing this whole time: |
| 12 |
|
| 13 |
If, as a user or an arch person, I get a src_test failure right now, I |
| 14 |
don't know whether this means "eek! Something's gone wrong, and I |
| 15 |
really need to fix this" or "oh, whoever maintains this package |
| 16 |
doesn't care". But with EAPI 2, I'll be able to know that a src_test |
| 17 |
failure really does mean "something's wrong". |
| 18 |
|
| 19 |
-- |
| 20 |
Ciaran McCreesh |
Archives