From owner-freebsd-ports@FreeBSD.ORG Sat May 5 19:26:20 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4354316A401 for ; Sat, 5 May 2007 19:26:20 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3331513C458 for ; Sat, 5 May 2007 19:26:20 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 15B9C1A4DB4; Sat, 5 May 2007 12:26:58 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 46F2D516FA; Sat, 5 May 2007 15:26:19 -0400 (EDT) Date: Sat, 5 May 2007 15:26:18 -0400 From: Kris Kennaway To: Mike Durian Message-ID: <20070505192618.GA67138@xor.obsecurity.org> References: <200705051254.45659.durian@shadetreesoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705051254.45659.durian@shadetreesoftware.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-ports@freebsd.org Subject: Re: How to manage pkg-plists when two ports install the same files 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, 05 May 2007 19:26:20 -0000 On Sat, May 05, 2007 at 12:54:44PM -0600, Mike Durian wrote: > I have just noticed that both net/sipxtacklib and net/sipxcalllib > install the some of the same header files. How to I manage pkg-plists > for both ports and keep tinderbox happy? > > If I list the files in both packing lists, the first port to > deinstall removes the files. Then tinderbox gets unhappy because > files that were present before the port was deinstalled are now > missing. Only one port is allowed to install such files. If they both need to use it then either "ownership" of the common file needs to move into a common dependency, or the ports be marked with CONFLICTS so they can't be installed on top of each other. Kris