| 1 |
Hi, |
| 2 |
|
| 3 |
Today I emerged "tightvnc" and it installed "tightvnc-1.2.3-r2.ebuild" |
| 4 |
by default. |
| 5 |
|
| 6 |
I turns out this version of the "vncserver" is broken and leads to a |
| 7 |
garbled image on the PPC (I gather from the web that it has something |
| 8 |
to do with endian-ness). I then emerged "tightvnc-1.2.6.ebuild" and it |
| 9 |
solved the problem. |
| 10 |
|
| 11 |
Anyhow, that ebuild for this newer (fixed) version lacks the "ppc" |
| 12 |
keyword and does not install by default. You get the broken one |
| 13 |
instead. Perhaps this ought to be changed. |
| 14 |
|
| 15 |
Marcio Luis Teixeira |
| 16 |
|
| 17 |
|
| 18 |
|
| 19 |
PS: I've noticed a lot of packages are *not* marked with a ppc keyword |
| 20 |
and emerge often fails to find them. This is frustrating. Is there a |
| 21 |
reason why packages aren't marked "ppc" to begin with and the keywords |
| 22 |
removed only if it turns out to be broken? |
Archives