From owner-freebsd-ports@FreeBSD.ORG Mon Feb 7 20:13:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65708106566C for ; Mon, 7 Feb 2011 20:13:38 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 33F448FC0C for ; Mon, 7 Feb 2011 20:13:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 53EF550A26; Mon, 7 Feb 2011 20:13:37 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZM3Qed-29a2; Mon, 7 Feb 2011 20:13:37 +0000 (GMT) Received: from nyi.unixathome.org (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 7ADDE509F3; Mon, 7 Feb 2011 20:13:36 +0000 (GMT) Received: from 68.64.144.221 (SquirrelMail authenticated user dan) by nyi.unixathome.org with HTTP; Mon, 7 Feb 2011 15:13:37 -0500 Message-ID: <003928a98b026742d7d6cb3a27fa7c2a.squirrel@nyi.unixathome.org> In-Reply-To: <4D50188A.9030909@bsdforen.de> References: <4D50188A.9030909@bsdforen.de> Date: Mon, 7 Feb 2011 15:13:37 -0500 From: "Dan Langille" To: "Dominic Fandrey" User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: bf1783@gmail.com, "b. f." , freebsd-ports@freebsd.org, Dan Langille Subject: Re: What ports require this port? 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: Mon, 07 Feb 2011 20:13:38 -0000 On Mon, February 7, 2011 11:06 am, Dominic Fandrey wrote: > On 07/02/2011 03:01, b. f. wrote: >>> Over the weekend, a new feature was added to FreshPorts BETA. A port >>> now lists all ports that require it. This code will eventually move to >>> production after it's been running on on the beta site for a while. >>> >>> Notes: >>> >>> * The code uses the output of make -V RUN_DEPENDS -V LIB_DEPENDS -V >>> BUILD_DEPENDS >> >> If you're going to include BUILD_DEPENDS, then you should also use -V >> PATCH_DEPENDS -V FETCH_DEPENDS. > > Maybe it should be split into "The package requires" only listing the > INSTALL_DEPENDS and "The port requires" listing all dependencies. Your post, combined with new information, has raised a question. Consider 'make build-depends-list' and 'make run-depends-list' for devel/glib20: $ make build-depends-list /usr/ports/devel/gettext /usr/ports/devel/gmake /usr/ports/devel/libtool /usr/ports/devel/pcre /usr/ports/devel/pkg-config /usr/ports/lang/perl5.8 /usr/ports/lang/python26 $ make run-depends-list /usr/ports/devel/gettext /usr/ports/devel/pcre /usr/ports/devel/pkg-config /usr/ports/lang/perl5.8 /usr/ports/lang/python26 The run-depends-list contains all of the information from LIB_DEPENDS and RUN_DEPENDS. The build-depends-list includes all of BUILD_DEPENDS, PATCH_DEPENDS, FETCH_DEPENDS, and EXTRACT_DEPENDS. I am tempted to alter FreshPorts and abandon all *_DEPENDS and use just run-depends-list and build-depends-list. How much value is there is having all of this information separated into individual _DEPENDS? -- Dan Langille -- http://langille.org/