On 8 July 2012 00:38, Pacho Ramos <firstname.lastname@example.org> wrote: > After reading:
> Looks like there is not consensus about how to handle this cases,
> probably a PROPERTIES variable for this would help :-/
> Any ideas on this kind of issue?
I've been handling it on the perl-experimental overlay by specifying
SRC_TEST is a perl-module.eclass variable that controls weather or not
to run the packages inbuilt tests.
Its not anywhere in official capacity, but I think my approach is
sane-ish somewhat, just needs better native support in my opinion. https://github.com/kentfredric/perl-experimental/blob/eclass-moretests/eclass/perl-module.eclass#L283
I think it would be nice to mask packages by their test failure
expectancy, for instance, mask packages that the tests are known to
fail on, or have tests turned on for all packages except packages
where failures are expected from tests. ( There are a few packages
which will always fail tests apparently, and it would be nice to
indicate as such in the ebuild ).
This way you can also probably opt for:
a) installing only packages which don't require network for their tests
b) only testing packages which don't require network for their tests
I've also thought it might be nice to have a way to enable testing
every time I install a ~amd64 package, instead of having a wide
spectrum "all or nothing" approach.
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" http://kent-fredric.fox.geek.nz