| 1 |
On 04/06/10 17:23, Neil Bothwick wrote: |
| 2 |
> On Tue, 06 Apr 2010 10:11:02 +1000, Lie Ryan wrote: |
| 3 |
> |
| 4 |
>> Anyway, I've been thinking about this for some time that turning on |
| 5 |
>> FEATURES="test" globally seems quite impractical for many users |
| 6 |
> |
| 7 |
> FEATURES=test is not meant to be used by users, it is a developer |
| 8 |
> setting, and they would only enable it for packages they maintain and |
| 9 |
> then only when they ant to run the tests. |
| 10 |
|
| 11 |
But most developers do not have the resources to test on all |
| 12 |
combinations of platforms. If the barrier for FEATURES="test" can be |
| 13 |
lowered, then everyone that wants to be a global tester can do it |
| 14 |
without sacrificing too muchs (plus they can control how much time they |
| 15 |
want to contribute) and this benefits all open-source software as a |
| 16 |
whole. Lowering barrier for testing also encourages developers to write |
| 17 |
unittest who would otherwise hand-waving it since they now know their |
| 18 |
unittest will really be testing the program's true correctness instead |
| 19 |
of an platform dependent correctness. Probably enabling "test" by |
| 20 |
default is too much to ask though. |
| 21 |
|
| 22 |
>> Due to this problem, I think portage could have a test policy feature so |
| 23 |
>> people can have finer control to filter out test suites that they don't |
| 24 |
>> want to run. This way globally FEATURES="test" can be more feasible for |
| 25 |
>> most users (and probably can sometime be turned on by default). |
| 26 |
> |
| 27 |
> You can set features on a per-package basis by putting FEATURES="blah" |
| 28 |
> into /etc/portage/env/category/package. |
Archives