Date: Mon, 7 Feb 2011 23:46:49 -0600 From: Ade Lovett <ade@FreeBSD.org> To: Dan Langille <dan@langille.org> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: What ports require this port? Message-ID: <01F78B4E-AAAE-4E61-AD4A-2965A5D7F62D@FreeBSD.org> In-Reply-To: <003928a98b026742d7d6cb3a27fa7c2a.squirrel@nyi.unixathome.org> References: <AANLkTikg5cLG9B07bzL00p6q-uJ1KyiKEt5rWae50w-r@mail.gmail.com> <4D50188A.9030909@bsdforen.de> <003928a98b026742d7d6cb3a27fa7c2a.squirrel@nyi.unixathome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 07, 2011, at 14:13 , Dan Langille wrote: > I am tempted to alter FreshPorts and abandon all *_DEPENDS and use = just > run-depends-list and build-depends-list. >=20 > How much value is there is having all of this information separated = into > individual _DEPENDS? It's critical for things like tinderbox and the package building = clusters, where each fetch/extract/patch/configure/build/install phase = is discrete, only installs the relevant dependencies, and so on to = ensure a full clean-room environment. In terms of what you're looking at for this particular project, = *-depends-list will almost certainly suffice, and it'd be trivial to add = that into MakeCache (using targets, rather than variable outputs via -V) Indeed, the following two lines from MakeCache should be a hint: # A close approximation to the 'run-depends-list' target sub RunDependsList ... :) -aDe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01F78B4E-AAAE-4E61-AD4A-2965A5D7F62D>