From owner-freebsd-ports Fri Aug 3 15: 4:11 2001 Delivered-To: freebsd-ports@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 8C9E937B408 for ; Fri, 3 Aug 2001 15:04:08 -0700 (PDT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 3DDFC541D; Sat, 4 Aug 2001 00:04:04 +0200 (CEST) Date: Sat, 4 Aug 2001 00:04:04 +0200 From: Anton Berezin To: John Merryweather Cooper Cc: FreeBSD-PORTS Subject: Re: How to tell when BUILD vs. RUN_DEPENDS is appropriate/more appropriate Message-ID: <20010804000404.B17409@heechee.tobez.org> Mail-Followup-To: Anton Berezin , John Merryweather Cooper , FreeBSD-PORTS References: <20010730201214.O82760@johncoop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730201214.O82760@johncoop>; from jmcoopr@webmail.bmi.net on Mon, Jul 30, 2001 at 08:12:14PM -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jul 30, 2001 at 08:12:14PM -0700, John Merryweather Cooper wrote: > As I'm going through the list of broken "orphaned" ports on bento, I'm > noticing that a number of ports (e.g. dhcpconf and flowscan) have > mtree problems that appear to be related to PERL5 or PYTHON usage by a > dependent port build. However, the "parent" port does not seem to get > credit for then underlying dependency on perl, python etc. > Now, LIB_DEPENDS is (usually) pretty easy--if a port needs a library > that's not already on the system, one is really going to know it when > the linker fails. But differentiating between a BUILD_DEPENDS and a > RUN_DEPENDS seems to be a much grayer area. How to resolve this such > that not only does a port build correctly, but bento doesn't also > complain about what appears to be the entire tree for python or perl > not being in the pkg-plist. There are two useful things which might be done. First, I think it is a good idea to modify buildscript in such a way that it will delete the BUILD_DEPENDS packages immediately before trying to delete a package itself. In this way, in the particular case of dhcpconf, we'll get a clear indication that it is devel/newt which is broken, not dhcpconf. Thus, it will take much less time to find out what's going on. Second, instead of printing the extras and then the whole $prefix, it makes sense to `expand' extras and print just them. =Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message