VNC v4b4 has been around for a while, but the only ebuild I can find for it is under net-misc/tightvnc (not net-misc/vnc). And even this ebuild requires ~amd64. I am running a Althon XP, not an amd64 platform, but I emerged the v4 ebuild anyway (by setting ~amd64). It seems to work fine, though I only run the server (with a Win32 client). Perhaps a ~x86 keyword could be added. Other people who run the client seem to have issues with this ebuild though (see the comments in bug 32742). Adding an v4b4 ~x86 ebuild for net-misc/vnc as well as for net-misc/tightvnc would reduce confusion. Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** This bug has been marked as a duplicate of 32742 ***
My bug is not a duplicate of bug 32742. It complains that the ebuild in tightvnc is in the wrong place. I say it is in the right place, but that it has problems (no ~x86 & the problems mentioned after the resolution of bug 32742) and that there should be *another* ebuild for reguler vnc v4 in net-misc/vnc.
net-misc/vnc-4.0 has just been added to the tree.
