Date: Mon, 12 Jul 2004 21:37:54 -0400 From: Tom McLaughlin <tmclaugh@sdf.lonestar.org> To: Cyrille Lefevre <clefevre-lists@9online.fr> Cc: james@now.ie Subject: Re: Triple VNC Message-ID: <1089682674.703.36.camel@compass.straycat.dhs.org> In-Reply-To: <044601c4682a$9b8709d0$7890a8c0@dyndns.org> References: <40F1AB4F.3050605@domar.pl> <1089587801.703.46.camel@compass.straycat.dhs.org> <044601c4682a$9b8709d0$7890a8c0@dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2004-07-12 at 12:09, Cyrille Lefevre wrote: > "Tom McLaughlin" <tmclaugh@sdf.lonestar.org> wrote: > > On Sun, 2004-07-11 at 17:04, Bruno Czekay wrote: > [snip] > > The first problem I see is you install the tightvnc package and it > > creates bin/vncviewer which is a symlink to bin/vncviewer-tight and then > > you install realvnc. I believe that if you overwrite the existing > > symlink you will overwrite the symlink target. So by installing > > realvnc's bin/vncviewer you will overwrite tightvnc's > > bin/vncviewer-tight. I haven't tried this with any ports, simply > > copying files around and copying to the symlink overwrote the target > > file. > > a well done package could easily handle this issue by first removing the > symlink and by installing its own one. a better way would be to install > all of them using a separate name and to have a separate startup script > for each of them w/ separate startup variables for the server side, and > to have a wrapper for the client side as for mozilla. > > <snip> Okay, would the wrapper script then be bin/vncviewer? Which package owns the script and what happens if the owner package is removed, how does that affect the other vnc versions installed? Personally I tend to be leery of anything fancy in ports to make them play nice with others. That's my bias there. Thanks. :) Tom > > Cyrille Lefevre.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1089682674.703.36.camel>