Ciaran McCreesh wrote:
> What, you're saying they all ship with test suites that exist but don't
> work?
anything that takes more than 10m to test is broken from an user point
of view: you want the application, not having it tested.
I'd rather keep it in features since tests are _optional_, not necessary
to use the applications, just a waste of user time if they aren't
concerned (e.g.: nobody but some would care about ffmpeg failing to do
bit exact decoding of an ${fringe codec} nobody but who is developing it
uses, and surely will be angry at me not being able to get those 20%
speed improvements on h264).
>
>> I don't think it shoud be part of the spec even if you don't have test
>> broken on delivery.
>
> src_test is already part of the spec, and ebuilds are supposed to
> either support it or RESTRICT it. I'm just proposing that EAPI 1 be a
> lot stricter about it...
>
Adding more build time, requirements (yes, there are some tests that
needs more ram and cpu to complete than the actual build phase) w/out
ways to opt out is just hindering our users.
lu
--
Luca Barbato
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
[EMAIL PROTECTED] mailing list
