| 1 |
On 8 July 2012 00:38, Pacho Ramos <pacho@g.o> wrote: |
| 2 |
> After reading: |
| 3 |
> https://bugs.gentoo.org/show_bug.cgi?id=424719 |
| 4 |
> https://bugs.gentoo.org/show_bug.cgi?id=397973 |
| 5 |
> |
| 6 |
> Looks like there is not consensus about how to handle this cases, |
| 7 |
> probably a PROPERTIES variable for this would help :-/ |
| 8 |
> |
| 9 |
> Any ideas on this kind of issue? |
| 10 |
|
| 11 |
I've been handling it on the perl-experimental overlay by specifying |
| 12 |
SRC_TEST="network" |
| 13 |
|
| 14 |
SRC_TEST is a perl-module.eclass variable that controls weather or not |
| 15 |
to run the packages inbuilt tests. |
| 16 |
|
| 17 |
Its not anywhere in official capacity, but I think my approach is |
| 18 |
sane-ish somewhat, just needs better native support in my opinion. |
| 19 |
|
| 20 |
https://github.com/kentfredric/perl-experimental/blob/eclass-moretests/eclass/perl-module.eclass#L283 |
| 21 |
|
| 22 |
I think it would be nice to mask packages by their test failure |
| 23 |
expectancy, for instance, mask packages that the tests are known to |
| 24 |
fail on, or have tests turned on for all packages except packages |
| 25 |
where failures are expected from tests. ( There are a few packages |
| 26 |
which will always fail tests apparently, and it would be nice to |
| 27 |
indicate as such in the ebuild ). |
| 28 |
|
| 29 |
This way you can also probably opt for: |
| 30 |
a) installing only packages which don't require network for their tests |
| 31 |
b) only testing packages which don't require network for their tests |
| 32 |
|
| 33 |
I've also thought it might be nice to have a way to enable testing |
| 34 |
every time I install a ~amd64 package, instead of having a wide |
| 35 |
spectrum "all or nothing" approach. |
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
Kent |
| 43 |
|
| 44 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
| 45 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |
| 46 |
|
| 47 |
http://kent-fredric.fox.geek.nz |
Archives