From owner-freebsd-ports@FreeBSD.ORG Tue Jul 13 01:37:56 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 443D716A4CE for ; Tue, 13 Jul 2004 01:37:56 +0000 (GMT) Received: from straycat.dhs.org (h0050da134090.ne.client2.attbi.com [24.91.148.154]) by mx1.FreeBSD.org (Postfix) with SMTP id 808F043D2D for ; Tue, 13 Jul 2004 01:37:55 +0000 (GMT) (envelope-from tmclaugh@sdf.lonestar.org) Received: (qmail 3285 invoked from network); 13 Jul 2004 01:37:54 -0000 Received: from compass.straycat.dhs.org (HELO ?192.168.1.32?) (192.168.1.32) by alexandria.straycat.dhs.org with SMTP; 13 Jul 2004 01:37:54 -0000 From: Tom McLaughlin To: Cyrille Lefevre 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> Content-Type: text/plain Message-Id: <1089682674.703.36.camel@compass.straycat.dhs.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 12 Jul 2004 21:37:54 -0400 Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: Bruno Czekay cc: james@now.ie Subject: Re: Triple VNC X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 01:37:56 -0000 On Mon, 2004-07-12 at 12:09, Cyrille Lefevre wrote: > "Tom McLaughlin" 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. > > 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.