From owner-freebsd-ports@FreeBSD.ORG Tue May 9 21:43:55 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 3D9F716A4D0 for ; Tue, 9 May 2006 21:43:55 +0000 (UTC) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BC9343D58 for ; Tue, 9 May 2006 21:43:54 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [128.2.136.137] (SKKUKUK.ECE.CMU.EDU [128.2.136.137]) by bache.ece.cmu.edu (Postfix) with ESMTP id 00C8F7F; Tue, 9 May 2006 17:43:52 -0400 (EDT) In-Reply-To: References: <20060508200926.GA6005@daemons.gr> <1147119806.18944.59.camel@ikaros.oook.cz> <20060508203709.GA32661@daemons.gr> <747dc8f30605090333s39680f91l79a2beddd2f8b829@mail.gmail.com> <20060509144751.GU3099@numachi.com> <790a9fff0605090831o4e8efbaarf53ca844bb348758@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Brandon S. Allbery KF8NH" Date: Tue, 9 May 2006 17:43:51 -0400 To: Garance A Drosihn X-Mailer: Apple Mail (2.749.3) Cc: Scot Hetzel , freebsd-ports@freebsd.org Subject: Re: ports structure -- problem with pkgtools.conf 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: Tue, 09 May 2006 21:43:55 -0000 On May 9, 2006, at 4:50 PM, Garance A Drosihn wrote: > At 10:31 AM -0500 5/9/06, Scot Hetzel wrote: >> The problem with pkgtools.conf (and all the other port >> management tools) is that it only works for the port >> that you are currently building. If that port has >> dependancies, the settings in pkgtools.conf for the >> dependancies are not applied to the dependent port. >> Instead you need to build the dependent ports first. > > Seems to me I have hit occasions where portupgrade > did not seem to catch some dependency, but that > dependency was in fact built when I went to build > my original target-port. But I forget in what > circumstances that has come up. That's a different bug: portupgrade doesn't update its internal database to account for dependencies having been built by the ports system itself. I've been bitten by both of these, and have since migrated to make.conf instead of pkgtools.conf (this still leaves the above bug, but I work around it with "FORCE_PKG_REGISTER=1 portupgrade ..." --- probably this has risks though). -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH