Date: Tue, 9 May 2006 16:50:45 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: "Scot Hetzel" <swhetzel@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: ports structure -- problem with pkgtools.conf Message-ID: <p06230927c086afe16971@[128.113.24.47]> In-Reply-To: <790a9fff0605090831o4e8efbaarf53ca844bb348758@mail.gmail.com> References: <20060508200926.GA6005@daemons.gr> <1147119806.18944.59.camel@ikaros.oook.cz> <20060508203709.GA32661@daemons.gr> <747dc8f30605090333s39680f91l79a2beddd2f8b829@mail.gmail.com> <20060509144751.GU3099@numachi.com> <790a9fff0605090831o4e8efbaarf53ca844bb348758@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Seems to me I have hit occasions where portupgrade did not seem to catch some dependency, but that dependency was in fact built when I went to build my original target-port. But I forget in what circumstances that has come up. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06230927c086afe16971>