Date: Tue, 13 Jul 2004 13:40:46 -0500 From: "Brandon D. Valentine" <brandon@dvalentine.com> To: Bruno Czekay <bruno@domar.pl> Cc: Cyrille Lefevre <clefevre-lists@9online.fr> Subject: Re: Triple VNC Message-ID: <20040713184046.GA20629@brandon.dvalentine.com> In-Reply-To: <40F38B09.8080205@domar.pl> References: <40F1AB4F.3050605@domar.pl> <1089587801.703.46.camel@compass.straycat.dhs.org> <044601c4682a$9b8709d0$7890a8c0@dyndns.org> <1089682674.703.36.camel@compass.straycat.dhs.org> <054201c46887$563a46f0$7890a8c0@dyndns.org> <1089693254.702.37.camel@compass.straycat.dhs.org> <40F38B09.8080205@domar.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 13, 2004 at 09:11:05AM +0200, Bruno Czekay wrote: > Anyway, one question again. Assuming I'm installing all three ports, > which one will be seen as vncviewer/-server etc? Real VNC or the last > one I've installed? I would suggest you look at the way perl in FreeBSD now works. Have all three VNC ports depend on the vnc-wrapper port (which itself should probably just depend on nothing). The vnc-wrapper port installs a command called use.vnc that sets up symlinks for vncviewer, vncserver, etc to the set of binaries indicated as argv[1] to use.vnc, similar to the way use.perl works. pkg-message in all three VNC ports should tell the user something like "to use this VNC package as your default VNC package, type use.vnc tight". You could even add optional flags to use.vnc that would let the user do things like specify that vncserver be linked to tightVNC but vncviewer to tridia or whatever crazy setup that user wanted. HTH, Brandon D. Valentine -- brandon@dvalentine.com http://www.geekpunk.net Pseudo-Random Googlism: july is mixed nut month
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040713184046.GA20629>