| 1 |
> > > The arch teams have been pushing for this for a long time. They're |
| 2 |
> > > trying to get this enforced, but are having limited success because |
| 3 |
> > > there's no way for FEATURES=test to become widely used that won't |
| 4 |
> > > lead to broken user systems. Moving src_test to be always on in |
| 5 |
> > > future EAPIs is an easy way of helping arch teams achieve this goal |
| 6 |
> > > without breaking anyone's system in the meantime. |
| 7 |
> > |
| 8 |
|
| 9 |
Hmm, as an arch tester, i completely agree that packages where src_test |
| 10 |
fails are an annoyance. However, I would not suggest to activate |
| 11 |
src_test by default, as for normal users, it just introduces another |
| 12 |
source of potential defects, without that much benefits. Instead, i |
| 13 |
think that arch teams should refuse to stable packages that fail with |
| 14 |
FEATURES=test and thus encourage ebuild developers to either fix their |
| 15 |
tests, or to deactivate them explicitly. |
| 16 |
|
| 17 |
Matthias |
| 18 |
|
| 19 |
-- |
| 20 |
gentoo-dev@g.o mailing list |
Archives