From owner-freebsd-ports@FreeBSD.ORG Tue May 9 20:50:50 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 9E89F16A4C7 for ; Tue, 9 May 2006 20:50:50 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3657F43D45 for ; Tue, 9 May 2006 20:50:50 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.1/8.13.0) with ESMTP id k49KokML022948; Tue, 9 May 2006 16:50:48 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <790a9fff0605090831o4e8efbaarf53ca844bb348758@mail.gmail.com> 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> Date: Tue, 9 May 2006 16:50:45 -0400 To: "Scot Hetzel" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.4 Cc: 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 20:50:51 -0000 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. > >Where as putting the variable into make.conf, will >allow the dependent port to always build with that >setting. Hmm. I don't think I have been bitten by this, but then I usually do a 'portupgrade -Rr -n' check on whatever I want to build, so I can see what dependencies need to be rebuilt first. Is this really a problem that other people have hit frequently? 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. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu