From owner-freebsd-ports@FreeBSD.ORG Sat Nov 4 05:47:13 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org 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 DAFB616A412 for ; Sat, 4 Nov 2006 05:47:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 2D3E643D5D for ; Sat, 4 Nov 2006 05:47:13 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 17912 invoked by uid 399); 4 Nov 2006 05:47:12 -0000 Received: from localhost (HELO ?192.168.0.11?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 4 Nov 2006 05:47:12 -0000 Message-ID: <454C295E.8060002@FreeBSD.org> Date: Fri, 03 Nov 2006 21:47:10 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.7 (X11/20061103) MIME-Version: 1.0 To: Matthew Seaman References: <454BB10E.4020900@infracaninophile.co.uk> In-Reply-To: <454BB10E.4020900@infracaninophile.co.uk> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Charles Sprickman , freebsd-ports@freebsd.org Subject: Re: [nycbug-talk] creating "local" ports (fwd) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Nov 2006 05:47:13 -0000 Matthew Seaman wrote: > That's a generic problem with ports -- instead of registering a > dependency on the package that provided the file that satisfied the > test specified by the FOO_DEPENDS variable in the port Makefile, the > dependency is registered on the default package to install to resolve > the dependency as shown in the second half of the FOO_DEPENDS line. That's both a positive and a negative. The positive is that the ports infrastructure works transparently when a dependency is satisfied by another port at build/run time. But you're right, it doesn't have a mechanism for translating that knowledge into something to record in the +CONTENTS file. > No idea if either portmaster or portmanager have any similar > alternate dependency functionality though. What portmaster does is to read CONFLICTS for each port that is depended on, and then look to see if you have one of those ports installed. If it does, it treats that port as the one to satisfy the dependency for purposes of looking for updates, building your port, etc. It does not twiddle with the DEPORIGIN in the +CONTENTS file however. hth, Doug -- This .signature sanitized for your protection