From owner-freebsd-ports@FreeBSD.ORG Mon Jul 12 16:09:30 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 3D88416A4CE for ; Mon, 12 Jul 2004 16:09:30 +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 89B1543D2D for ; Mon, 12 Jul 2004 16:09:29 +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 9F96814B9FA; Mon, 12 Jul 2004 18:13:00 +0200 (CEST) Message-ID: <044601c4682a$9b8709d0$7890a8c0@dyndns.org> From: "Cyrille Lefevre" To: "Tom McLaughlin" , "Bruno Czekay" References: <40F1AB4F.3050605@domar.pl> <1089587801.703.46.camel@compass.straycat.dhs.org> Date: Mon, 12 Jul 2004 18:09:27 +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: 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: Mon, 12 Jul 2004 16:09:30 -0000 "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. > The second problem I see is which package owns bin/vncviewer? Both > would own bin/vncviewer according to their package lists and both would > want to remove the file. You could do away with the symlink and have > tightvnc simply install just bin/vncviewer-tight but that creates a > problem for frontends like tsclient which look for a vncviewer binary. > Now someone is forced to install realvnc to use tsclient when they > already have tightvnc. something like : #!/bin/sh if [ -f ${HOME}/.Xvncviewer ]; then . ${HOME}/.Xvncviewer fi if [ -z "${VNCVIEWER}" ] || [ ! -x ${VNCVIEWER} ]; then vncviewers="tight tridia real" unset VNCVIEWER for vncviewer in ${vncviewers}; do VNCVIEWER=%%PREFIX%%/bin/vncviewer-${vncviewer} if [ -x ${VNCVIEWER} ]; then echo VNCVIEWER=${VNCVIEWER} > ${HOME}/.Xvncviewer break; fi done fi if [ -z "${VNCVIEWER}" ] || [ ! -x ${VNCVIEWER} ]; then echo >&2 "$0: unable to find a valid VNC viewer!" echo >&2 "$0: please, install one of the following VNC package first:" echo >&2 "$0: tridiavnc, tightvnc or (real) vnc using pkg_add -r" exit 1 fi exec ${VNCVIEWER} "$@" > I think leaving them the way they are is probably the best way to go. Cyrille Lefevre. -- home: mailto:cyrille.lefevre@laposte.net