I use VNC a hell of a lot. I really like TightVNC's ability to squeeze through small amounts of bandwidth but now I need to use RealVNC's ability to support GLX and the x0vncserver idea could be useful as well. The problem is they share the same names in /usr/bin. Could we introduce a USE flag that could rename them to stuff like tight-vncviewer and real-vncviewer so both could be installed at the same time? Perhaps provide symlinks to one or the other (maybe the first one installed?) to provide compatibility. If not then the ebuilds should at least block each other.
I've since discovered XF4VNC, which seems to have the functionality of both. I guess there's no need for this now.
Even though the reporter now thinks otherwise, I see this as an issue. It would be good, if it were possible to install both TightVNC and VNC. Right now, it's not possible: >>> Completed installing vnc-4.0 into /var/tmp/portage/vnc-4.0/image/ * checking 14 files for package collisions existing file /usr/bin/Xvnc is not owned by this package existing file /usr/bin/vncpasswd is not owned by this package existing file /usr/bin/vncserver is not owned by this package existing file /usr/bin/vncviewer is not owned by this package existing file /usr/share/man/man1/Xvnc.1.gz is not owned by this package existing file /usr/share/man/man1/vncpasswd.1.gz is not owned by this package existing file /usr/share/man/man1/vncserver.1.gz is not owned by this package existing file /usr/share/man/man1/vncviewer.1.gz is not owned by this package * spent 0.139362096786 seconds checking for file collisions * This package is blocked because it wants to overwrite * files belonging to other packages (see messages above). * If you have no clue what this is all about report it * as a bug for this package on http://bugs.gentoo.org package net-misc/vnc-4.0 NOT merged No package files given... Grabbing a set. [20:27:41 alexander@server:~/Eigene_Dateien/Eigene Bilder/Screenshots] $ epm -qf /usr/bin/Xvnc /usr/bin/vncpasswd /usr/bin/vncserver /usr/bin/vncviewer /usr/share/man/man1/Xvnc.1.gz /usr/share/man/man1/vncpasswd.1.gz /usr/share/man/man1/vncserver.1.gz /usr/share/man/man1/vncviewer.1.gz tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 tightvnc-1.3_alpha5 Please change severity from Enhancement to Normal. Suggest to add something like "file-collision" to summary.
I also think this is necessary. I recently had a problem with the vnc from realvnc.com and tightvnc fixed it. I'd really like to not have to uninstall them, but instead just run something like vnc-config.
The Mac-on-linux (mol) use flag "vnc" demands 'net-misc/vnc' but 'net-misc/tightvnc' could replace it. The problem is that both utilities are blocked each other.
Perhaps something like 'eselect vnc set {tight|real|...}'?
This should be possible
does the same with XF4VNC...please update the title
realvnc is getting punted
+1 for eselect functionality. :)
Hey guys. I needed this too so I modified the ebuilds for tightvnc and tigervnc to prefix the names of the binaries, man pages and icons with "tight" or "tiger" respectively. As a bonus, I created an eselect module to manage symlinks from the normal names Both are somewhat quick and dirty, you have been warned! The eselect module is mostly ripped off from the kernel eselect module. If anyone wants to modify other vnc ebuilds, that would be great. I only modified one version of each package, so feel free to migrate the changes on your own.
Created attachment 258411 [details] tigervnc ebuild
Created attachment 258412 [details] tightvnc ebuild
Created attachment 258414 [details] vnc eselect module. usage is obvious enough
If you still need this, please provide updated ebuilds if possible and we will see if we can finally introduce them :/
