From owner-freebsd-ports@FreeBSD.ORG Fri Feb 3 19:55:09 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 D734F16A423 for ; Fri, 3 Feb 2006 19:55:09 +0000 (GMT) (envelope-from dave-lists-freebsd-ports@weller-fahy.com) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B23F43D73 for ; Fri, 3 Feb 2006 19:55:05 +0000 (GMT) (envelope-from dave-lists-freebsd-ports@weller-fahy.com) Received: from p508a2584.dip0.t-ipconnect.de ([80.138.37.132] helo=weller-fahy.com) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1F571L-0003sS-Lm for freebsd-ports@freebsd.org; Fri, 03 Feb 2006 14:55:04 -0500 Received: (qmail 27452 invoked by uid 1001); 3 Feb 2006 19:55:16 -0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 80.138.37.132 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: sinecure Date: Fri, 3 Feb 2006 20:55:16 +0101 From: "David J. Weller-Fahy" To: freebsd-ports@freebsd.org Message-ID: <20060203195453.GB3857@weller-fahy.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <43D610B6.5080008@FreeBSD.org> <43DE40FE.6000507@ebs.gr> <43DE6C65.9040306@FreeBSD.org> <43DE7652.9050807@ebs.gr> <43DF346B.407@FreeBSD.org> <43DF40BC.4060600@ebs.gr> <43E2B3A6.9060508@FreeBSD.org> <43E2B530.4050500@FreeBSD.org> <20060203065504.GA3857@weller-fahy.com> <43E31808.6070205@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43E31808.6070205@FreeBSD.org> X-URL-Me: http://weller-fahy.com X-Accept-Language: en X-Location: Germany, =?iso-8859-1?Q?H=C3=B6ngen?= =?iso-8859-1?Q?=2C?= Pfarrer-Meising-Str. User-Agent: Mutt/1.5.11 Subject: Re: New /bin/sh based script to manage ports 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: Fri, 03 Feb 2006 19:55:10 -0000 * Doug Barton [2006-02-03 09:45 +0100]: > This depends on which direction you're approaching the problem from. > When building a port, the check for whether the dependencies of the > port are up to date uses the list from 'make all-depends-list', which > will include build dependencies. I had missed that part of the script on my (brief) read through. Thanks for pointing it out. It makes sense that you'd take all dependencies into account at the port level. > However, once a port has been built and installed successfully, the > list of ports which have a dependency on the updated port is cross > checked between the +REQUIRED_BY in the package directory and the > +CONTENTS files of the other installed ports. In this way we can be > sure that all appropriate dependencies are recorded, and updated. > Since BUILD_DEPENDS are not registered in the +CONTENTS or > +REQUIRED_BY files, they don't show up at that stage, and portmaster > doesn't update information about them (because that information > doesn't exist). Ok, that's where I was confused. I had not thought out (fully) the implications of NOT using BUILD_DEPENDS when looking at installed packages, and thus assumed that 'something' would be missed. Your message, however, got me thinking about that, and I realized that I was wrong. Thanks for the enlightenment. ;] Well, back to tinkering with scripts and playing with ports. Regards, -- dave [ please don't CC me ]