1 |
Go for a. The widest and more consistent the testing, the better. |
2 |
|
3 |
Otherwise the day after tomorrow you'll get a bug from me that with |
4 |
$foo installed, $bar fails tests. |
5 |
Diego Elio Pettenò — Flameeyes |
6 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
7 |
|
8 |
|
9 |
On Sun, Jan 6, 2013 at 11:38 AM, Michał Górny <mgorny@g.o> wrote: |
10 |
> Hello, |
11 |
> |
12 |
> There are some Python packages which have a bunch of optional tests |
13 |
> utilizing external packages. For example, the dev-python/logilab-common |
14 |
> runs a few additional tests if dev-python/egenix-mx-base is installed; |
15 |
> if the package is not installed, it just skips those tests. |
16 |
> |
17 |
> Those tests can't be really considered 'heavy' or in any way suggesting |
18 |
> use of an additional USE flag. |
19 |
> |
20 |
> Do you believe that the ebuilds should: |
21 |
> |
22 |
> a) depend on all optional test dependencies conditionally to USE=test, |
23 |
> therefore always requesting the widest (and consistent) testing, |
24 |
> |
25 |
> b) not depend on the optional test dependencies, resulting in less |
26 |
> dependencies for most users but also a bit inconsistent test |
27 |
> experience, |
28 |
> |
29 |
> c) put the optional test dependencies behind an additional USE flag? |
30 |
> |
31 |
> -- |
32 |
> Best regards, |
33 |
> Michał Górny |