There are two vnc packages available: net-misc/vnc is official vnc from www.realvnc.com net-misc/tightvnc is vnc from www.tightvnc.com There is now a net-misc/tightvnc-4.0_beta*.ebuild even though it really is a release from realvnc and should be a net-misc/vnc-4.0_beta*.ebuild The realvnc 4.0 release is incompatible with tighvnc 1.2.9 (the current stable) as it has a completely different commandline syntax and feature list. Reproducible: Always Steps to Reproduce: 1. check the HOMEPAGE of net-misc/tightvnc-4.0_beta20031031.ebuild 2. check the HOMEPAGE of net-misc/tightvnc-1.2.9-r1.ebuild 3. check the HOMEPAGE of net-misc/vnc-3.3.7.ebuild Actual Results: tightvnc 1.2.9 is correctly from tightvnc.com vnc 3.3.7 is correctly from realvnc.com tightvnc 4.0 is from realvnc.com
tightvnc-4.0_beta* is the realvnc.com sourcecode (from which tightvnc is derived from) + tightvnc CVS checkout patch. I'm only using the realvnc tarball as a base to minimze the tightvnc CVS patch. Currently I'm running tightvnc-1.2.9 on my client and tightvnc-4.0_beta on the server and have no problems apart that when xscreensaver is locking my screen the vnc connection is dropped. Maybe 4.0 has problems on the x86 side, becuse I've only tried it on amd64.
I tried to build tightvnc-4.0_beta again. If the goal was to apply tightvnc patch over the realvnc 4.0 then I change my complaint. It seems that the tightvnc patch is not applied to the vncviewer client, instead the original vnc client is built. The original vnc client doesn't support the -via command line switch to tunnel the connections overs ssh, nor does it support the copyrect, tight, corre, rre or jpeg encodings which are the main reason why tightvnc exists.
*** Bug 38153 has been marked as a duplicate of this bug. ***
