From owner-freebsd-ports@FreeBSD.ORG Tue Jul 13 10:39:00 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 6EF4816A4CE for ; Tue, 13 Jul 2004 10:39:00 +0000 (GMT) Received: from worf.kerna.com (worf.kerna.com [194.106.143.118]) by mx1.FreeBSD.org (Postfix) with SMTP id 9A01C43D45 for ; Tue, 13 Jul 2004 10:38:59 +0000 (GMT) (envelope-from james@now.ie) Received: (qmail 21855 invoked by uid 1012); 13 Jul 2004 10:39:02 -0000 Date: Tue, 13 Jul 2004 11:39:02 +0100 From: James Raftery To: Bruno Czekay , Tom McLaughlin Message-ID: <20040713103902.GA21294@bender.kerna.ie> References: <054201c46887$563a46f0$7890a8c0@dyndns.org> <1089693254.702.37.camel@compass.straycat.dhs.org> <40F38B09.8080205@domar.pl> <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> <40F1AB4F.3050605@domar.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40F38B09.8080205@domar.pl> <1089693254.702.37.camel@compass.straycat.dhs.org> <40F1AB4F.3050605@domar.pl> cc: ports@FreeBSD.org cc: Cyrille Lefevre 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 10:39:00 -0000 On Sun, Jul 11, 2004 at 11:04:15PM +0200, Bruno Czekay wrote: > I wanted to make some tests between (Real) VNC, TightVNC and TridiaVNC > servers (run on FreeBSD) against their clients, installed both on > FreeBSD and Windows. But every package installs itself as Xvnc, > vncserver, vncviever etc. Wouldn't it be more useful, if enhanced > versions installed themselves as Xvnc-tight and Xvnc-tridia? Nice idea - it probably would be useful. I think that adding a wrapper port and then mucking about with which-port-depends-on-which is a degree of complication not really warranted for such a simple problem. I would propose adding a knob that would install the components of each port that normally have conflicting names instead with unique names. This has the added advantage of not changing any port's behaviour for the majority of users who won't need to do this. Now, `cd /usr/ports/net/tightvnc; make install' gives vncviewer, vncserver, etc. Something like: `make -DWITH_UNIQUE_NAMES install' might give vncviewer-tight, vncserver-tight, etc. Does that sound reasonable? On Tue, Jul 13, 2004 at 12:34:14AM -0400, Tom McLaughlin wrote: > I took a look at doing a port for vino (being in a VNC sort of mood) and > ran into how I could explicitly set a dependency on vnc over tightvnc or > tridiavnc and make sure that a previously installed tight/tridiavnc > wasn't satisfying the dependency. Hmm. If ${PREFIX}/bin/vncserver-real exists, use it. If not, and ${PREFIX}/bin/vncserver does, maybe use pkg_info to get the name of the port/package that owns it. If it's the wrong VNC, either add a dependency or prompt the user to install RealVNC. > Last problem I can see is tridiavnc uses share/vnc as does vnc. The > tighvnc package fortunately uses share/tightvnc. The first two would > have to be reconciled. Good point. That clash should be resolved regardless of any other changes. I would like to get RealVNC 4 into ports, but it's proving difficult. The new VNC server build process is being very uncooperative. Also on my list is to massage the non-i386 build fixes commited a while back for RealVNC over to get TightVNC and TridiaVNC compiling on non-i386 systems. Patches to get any of those done, or to make the unique names happen are very welcome! ATB, james -- Time flies like an arrow. Fruit flies like bananas.