1 |
On 2/21/10 10:40 AM, Thilo Bangert wrote: |
2 |
> "Paweł Hajdan, Jr." <phajdan.jr@g.o> said: |
3 |
>> The concern here may be that it's papering over the real problem, but |
4 |
>> the good side is that it'd make running with FEATURES=test much easier. |
5 |
> |
6 |
> which is a good thing, since more tests will be run. RESTRICT="test" |
7 |
> should always generate a repoman QA warning IMHO. |
8 |
|
9 |
+1 |
10 |
|
11 |
>> By the way, for packages that fail the test suite and refuse to disable |
12 |
>> it, I change the env locally so that FEATURES=-test (via |
13 |
>> /etc/portage/env). |
14 |
> |
15 |
> how many packages do you have in there? i usually just do it manually, so |
16 |
> i dont have easily available stats on how many packages are affected. |
17 |
|
18 |
I don't have a lot: |
19 |
|
20 |
$ tree /etc/portage/env |
21 |
/etc/portage/env |
22 |
|-- app-portage |
23 |
| `-- portage-utils.env |
24 |
|-- dev-libs |
25 |
| |-- boost.env |
26 |
| `-- libevent.env |
27 |
|-- dev-python |
28 |
| `-- pygtk.env |
29 |
|-- dev-scheme |
30 |
| `-- guile.env |
31 |
`-- sys-devel |
32 |
|-- binutils.env |
33 |
`-- libtool.env |
34 |
|
35 |
5 directories, 7 files |