From owner-freebsd-ports@FreeBSD.ORG Thu Jul 20 21:43:02 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 4FEE516A4DA for ; Thu, 20 Jul 2006 21:43:02 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB2FF43D46 for ; Thu, 20 Jul 2006 21:43:01 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 4BB4BD913C8 for ; Thu, 20 Jul 2006 17:43:00 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by frontend3.internal (MEProxy); Thu, 20 Jul 2006 17:43:02 -0400 X-Sasl-enc: 20Upb4J2RznujynYUJhV0Om1jkGn3CenvyVgtvDw/Nvx 1153431774 Received: from [192.168.1.2] (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id 66D3649C8 for ; Thu, 20 Jul 2006 17:42:54 -0400 (EDT) From: RW To: freebsd-ports@freebsd.org Date: Thu, 20 Jul 2006 22:42:55 +0100 User-Agent: KMail/1.9.3 References: <17598.52872.765184.211253@gromit.timing.com> In-Reply-To: <17598.52872.765184.211253@gromit.timing.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607202242.58399.list-freebsd-2004@morbius.sent.com> Subject: Re: conflicting dependency 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: Thu, 20 Jul 2006 21:43:02 -0000 On Thursday 20 July 2006 01:30, John E Hein wrote: > Let's say there are two ports A & B. > They both provide libfoo.so.1 (and so register CONFLICTS with each other). > > Now port C wants to use libfoo (and doesn't care if it gets it > from A or B). > > What does port C list in it's LIB_DEPENDS? > > What if it lists A and someone installs B... does A get registered as > the dependency when C is installed even though A is not installed? > > This must have been solved already... I just don't see where. Many of these problems have been avoided by abstracting the dependency into the portsystem itself. For example USE_OPENLDAP=yes delegates the choice of LDAP version to ports system. In most cases this is just a way of having a global default, but some are a bit more sophisticated. For example USE_GCC=3.4+ specifies version 3.4 or above of gcc; and there is some logic to determine whether this can be satisfied from the base system, or existing installed ports, before a new dependency is added. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"