xf4vnc ebuild provides the files /usr/bin/Xvnc and /usr/bin/vncviewer which conflict with tightvnc. Im using this ebuild just for /usr/lib/vnc.so , so maybe a good solution would be to make building of those components optional.
Created attachment 90906 [details] xf4vnc-4.3.0.999.ebuild Does this solve it for you? What do you say about useflag naming? Do we really need the useflags? Could we just leave everything out and use tightvnc since it is better?
(In reply to comment #1) > > What do you say about useflag naming? Do we really need the useflags? Could we > just leave everything out and use tightvnc since it is better? > tightvnc didn't work for me (at least some months ago): connecting from a tightvnc client running on windows it always blocked the X server (and the whole gentoo box as X runs with high priority). So I still need xf4vnc.
*** Bug 91333 has been marked as a duplicate of this bug. ***
thanks, I aded this ebuild to portage.
