m (Features/TightVNC moved to Features/TigerVNC: TightVNC has been forked and fork is called TigerVNC)
Revision as of 12:12, 2 March 2009
Replace RealVNC by TightVNC
Make TightVNC the default VNC client in Fedora.
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TightVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged.
- Name: Adam Tkac
- Targeted release: Fedora 11
- Last updated: 2009-01-21
- Percentage of completion: 95%
- tightvnc has been successfully included into distribution
TightVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.5 and supports more extensions. Fedora changes have to be carefully merged to TightVNC upstream and then we will use it as default Fedora vnc system.
Benefit to Fedora
vnc will have more features and will get benefit from upstream development instead of the current one man show in Fedora CVS. Overall quality should be better.
Merge Fedora changes to upstream and make TightVNC ready for Fedora
- Check that libvnc.so module to Xorg works fine
- Check that vnc installation works as expected
- Check that viewer works fine when you connect to Xvnc and to different servers (vino)
- Check that Xvnc works with other viewers (vinagre)
- Better encodings save bandwidth and processor time
- Viewer internationalization
- IPv6 support
Anaconda has to use tightvnc package instead vnc
- Use Fedora 10 codebase
- TightVNC is used as default VNC project. Package names were changed to tightvnc, tightvnc-server and tightvnc-server-module. Binary names are same as in previous version, libvnc.so module has been moved to tightvnc-server-module subpackage. Otherwise there should be no difference
Comments and Discussion