| 1 |
Le dimanche 21 février 2010 à 10:53 +0100, "Paweł Hajdan, Jr." a écrit : |
| 2 |
> On 2/21/10 10:40 AM, Thilo Bangert wrote: |
| 3 |
> > "Paweł Hajdan, Jr." <phajdan.jr@g.o> said: |
| 4 |
> >> By the way, for packages that fail the test suite and refuse to disable |
| 5 |
> >> it, I change the env locally so that FEATURES=-test (via |
| 6 |
> >> /etc/portage/env). |
| 7 |
> > |
| 8 |
> > how many packages do you have in there? i usually just do it manually, so |
| 9 |
> > i dont have easily available stats on how many packages are affected. |
| 10 |
> |
| 11 |
> I don't have a lot: |
| 12 |
> |
| 13 |
> $ tree /etc/portage/env |
| 14 |
> /etc/portage/env |
| 15 |
> |-- app-portage |
| 16 |
> | `-- portage-utils.env |
| 17 |
> |-- dev-libs |
| 18 |
> | |-- boost.env |
| 19 |
> | `-- libevent.env |
| 20 |
> |-- dev-python |
| 21 |
> | `-- pygtk.env |
| 22 |
|
| 23 |
pygtk should succeed, it does or did last time I touched it. Please |
| 24 |
report. |
| 25 |
|
| 26 |
> |-- dev-scheme |
| 27 |
> | `-- guile.env |
| 28 |
> `-- sys-devel |
| 29 |
> |-- binutils.env |
| 30 |
> `-- libtool.env |
| 31 |
|
| 32 |
libtool was fixed by diego a couple of weeks ago, it's probably not |
| 33 |
needed anymore. |
| 34 |
|
| 35 |
-- |
| 36 |
Gilles Dartiguelongue <eva@g.o> |
| 37 |
Gentoo |
Archives