From owner-freebsd-ports@FreeBSD.ORG Tue Jul 13 03:13:17 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 0677616A4CE for ; Tue, 13 Jul 2004 03:13:17 +0000 (GMT) Received: from huva.hittite.isp.9tel.net (huva.hittite.isp.9tel.net [62.62.156.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76F5243D49 for ; Tue, 13 Jul 2004 03:13:16 +0000 (GMT) (envelope-from clefevre-lists@9online.fr) Received: from pc2k (unknown [80.119.170.204]) by huva.hittite.isp.9tel.net (Postfix) with SMTP id 6B96314B679; Tue, 13 Jul 2004 05:16:53 +0200 (CEST) Message-ID: <054201c46887$563a46f0$7890a8c0@dyndns.org> From: "Cyrille Lefevre" To: "Tom McLaughlin" 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> Date: Tue, 13 Jul 2004 05:13:13 +0200 Organization: ACME MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 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 03:13:17 -0000 "Tom McLaughlin" wrote: > 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 yes > owns the script and what happens if the owner package is removed, how > does that affect the other vnc versions installed? as the mozilla (well, netscape) wrapper does, vnc-wrapper. so, there is no problem whatever which vncviewer is installed. see, netscape-wrapper for details. > Personally I tend to be leery of anything fancy in ports to make them > play nice with others. That's my bias there. Thanks. :) Cyrille Lefevre. -- mailto:clefevre-lists@9online.fr