On 2/21/10 10:40 AM, Thilo Bangert wrote: > "Paweł Hajdan, Jr." <[email protected]> said: >> The concern here may be that it's papering over the real problem, but >> the good side is that it'd make running with FEATURES=test much easier. > > which is a good thing, since more tests will be run. RESTRICT="test" > should always generate a repoman QA warning IMHO.
+1
>> By the way, for packages that fail the test suite and refuse to disable
>> it, I change the env locally so that FEATURES=-test (via
>> /etc/portage/env).
>
> how many packages do you have in there? i usually just do it manually, so
> i dont have easily available stats on how many packages are affected.
I don't have a lot:
$ tree /etc/portage/env
/etc/portage/env
|-- app-portage
| `-- portage-utils.env
|-- dev-libs
| |-- boost.env
| `-- libevent.env
|-- dev-python
| `-- pygtk.env
|-- dev-scheme
| `-- guile.env
`-- sys-devel
|-- binutils.env
`-- libtool.env
5 directories, 7 files
signature.asc
Description: OpenPGP digital signature
