Date: Fri, 01 Jun 2007 16:44:18 -0700 From: Doug Barton <dougb@FreeBSD.org> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-ports@freebsd.org Subject: Re: Uggg! Message-ID: <4660AF52.9090204@FreeBSD.org> In-Reply-To: <20070602002434.2069d5af@gumby.homeunix.com.> References: <20070601083345.GA48323@rot13.obsecurity.org> <10723ADA-FD53-45F8-BDFA-DBD98CBC212E@FreeBSD.org> <20070601170514.GA54912@rot13.obsecurity.org> <20070601.131415.74663752.imp@bsdimp.com> <4660857A.2030701@FreeBSD.org> <20070602002434.2069d5af@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
RW wrote:
> On Fri, 01 Jun 2007 13:45:46 -0700 Doug Barton <dougb@FreeBSD.org>
> wrote:
>
>> What you could do with portmaster is to pick a high level leaf
>> port with a lot of dependencies (something like firefox) and do
>> 'portmaster -aft /usr/ports/www/firefox' (make sure you specify
>> the directory in /usr/ports, not the pkg directory).
>
> How does that work?
portmaster doesn't rely on the dependency tracking in the port's
Makefile, it recurses the list itself. Since the the *-depends-lists
output directories in /usr/ports, and the -f switch to portmaster
means "[re]build it no matter what," portmaster will recurse all the
way down to the lowest level dependency/ies, and rebuild everything on
the way up.
> On the other hand, building everything in the all-depends-list may
> be wrong in other, more common, circumstances.
That's what the -t switch is for. It usually uses
build/run-depends-lists instead.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4660AF52.9090204>