Date: Sun, 06 Feb 2011 21:54:43 -0500 From: Dan Langille <dan@langille.org> To: bf1783@gmail.com Cc: "b. f." <bf1783@googlemail.com>, freebsd-ports@freebsd.org Subject: Re: What ports require this port? Message-ID: <4D4F5EF3.9030207@langille.org> In-Reply-To: <AANLkTi=GU1Qz3WV=rbh9R_WWCv-=wTZQSQQ9mbqH_Wi1@mail.gmail.com> References: <AANLkTikg5cLG9B07bzL00p6q-uJ1KyiKEt5rWae50w-r@mail.gmail.com> <AANLkTikDv4ee7g1WAu8-WaXwxU88m5j8SegGUtykkQfd@mail.gmail.com> <4D4F57C7.3030906@langille.org> <AANLkTi=GU1Qz3WV=rbh9R_WWCv-=wTZQSQQ9mbqH_Wi1@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/6/2011 9:50 PM, b. f. wrote:
> On 2/6/11, Dan Langille<dan@langille.org> wrote:
>> On 2/6/2011 9:03 PM, b. f. wrote:
>>> On 2/6/11, b. f.<bf1783@googlemail.com> wrote:
>
>>
>> While we're here... is there anything special about PATCH_DEPENDS,
>> FETCH_DEPENDS, and EXTRACT_DEPENDS that might be different than the
>> depends I'm already processing? They seem to be the same format:
>>
>> [dan@ngaio:/usr/ports/graphics/tifmerge] $ make -V EXTRACT_DEPENDS
>> tuc:/usr/ports/converters/tuc
>> /usr/local/bin/unzip:/usr/ports/archivers/unzip
>>
>> [dan@ngaio:/usr/ports/www/apache13-modssl] $ make -V PATCH_DEPENDS
>> /usr/local/bin/perl5.8.9:/usr/ports/lang/perl5.8
>> /usr/local/bin/perl5.8.9:/usr/ports/lang/perl5.8
>
> IIRC, they are the same ordered triple format. By the way, just
> because a port is in the *_DEPENDS of another port, doesn't
> necessarily mean that the first port must be installed to build the
> second port: sometimes the (usually absent) third element of the
> triplet can be used to override the default "install". So some
> *_DEPENDS, for example, just need to be fetched rather than installed.
> Others may just need to execute some simple target defined in the
> Makefile of the dependency. I don't know whether you want to include
> that level of detail in your Freshports pages.
I think you are referring to suffixes such as :patch, :fetch, :config.
FreshPorts ignores those entirely. It just lists the ports regardless
of those suffixes.
>> However, my manual searches to find a port which outputs a value for
>> 'make -V FETCH_DEPENDS' have failed so far. But I'm sure it will turn
>> up during my first few test runs.
>
> fgrep -e FETCH_DEPENDS -nH -r $PORTSDIR --include='*Makefile':
>
> ports/cad/kicad-devel/Makefile:83:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/cad/kicad-devel/Makefile:84:FETCH_DEPENDS+=
> bzr:${PORTSDIR}/devel/bazaar-ng
> ports/comms/wsjt/Makefile:66:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/devel/compiler-rt/Makefile:62:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/devel/llvm-devel/Makefile:89:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/graphics/seom/Makefile:47:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/graphics/yukon/Makefile:44:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/lang/clang-devel/Makefile:75:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/net/xorp-devel/Makefile:45:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/print/bsd_lpr/Makefile:33:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/www/trac-discussion/Makefile:31:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/www/trac-fivestarvote/Makefile:30:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/www/trac-math/Makefile:37:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/www/trac-ticketimport/Makefile:31:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
> ports/www/trac-vote/Makefile:30:FETCH_DEPENDS+=
> svn:${PORTSDIR}/devel/subversion
Find a Makefile containing FETCH_DEPENDS is one thing. Getting a value
from the default config settings is another. :) I wasn't explicit about
that, but I chose the words carefully.
--
Dan Langille - http://langille.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D4F5EF3.9030207>