Summary: | net-misc/tightvnc-4.0 ebuild is really a net-misc/vnc-4.0 placed in wrong place | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mikko Tiihonen <mikko.tiihonen> |
Component: | New packages | Assignee: | Daniel Ahlberg (RETIRED) <aliz> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | kelsall, vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mikko Tiihonen
2003-11-04 14:11:22 UTC
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. |