Date: Wed, 10 May 2006 00:42:10 +0100 From: RW <list-freebsd-2004@morbius.sent.com> To: freebsd-ports@freebsd.org Subject: Re: ports structure -- problem with pkgtools.conf Message-ID: <200605100042.12593.list-freebsd-2004@morbius.sent.com> In-Reply-To: <p06230927c086afe16971@[128.113.24.47]> References: <20060508200926.GA6005@daemons.gr> <790a9fff0605090831o4e8efbaarf53ca844bb348758@mail.gmail.com> <p06230927c086afe16971@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 09 May 2006 21:50, Garance A Drosihn wrote: > At 10:31 AM -0500 5/9/06, Scot Hetzel wrote: > >The problem with pkgtools.conf (and all the other port > >management tools) is that it only works for the port > >that you are currently building. If that port has > >dependancies, the settings in pkgtools.conf for the > >dependancies are not applied to the dependent port. > >Instead you need to build the dependent ports first. > > > >Where as putting the variable into make.conf, will > >allow the dependent port to always build with that > >setting. > > Hmm. > > I don't think I have been bitten by this, but then I > usually do a 'portupgrade -Rr -n' check on whatever I > want to build, so I can see what dependencies need to > be rebuilt first. Is this really a problem that other > people have hit frequently? The problem only occurs when a dependency is built the first time. I wouldn't expect this to be particularly noticable. The most significant options tend to be in leaf-ports, and important options in dependencies tend to translate into slave-ports.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605100042.12593.list-freebsd-2004>