ports structure -- problem with pkgtools.conf

[Brandon S. Allbery KF8NH]

On May 9, 2006, at 4:50 PM, 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.
>
> 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.

That's a different bug:  portupgrade doesn't update its internal  
database to account for dependencies having been built by the ports  
system itself.

I've been bitten by both of these, and have since migrated to  
make.conf instead of pkgtools.conf (this still leaves the above bug,  
but I work around it with "FORCE_PKG_REGISTER=1 portupgrade ..." ---  
probably this has risks though).

-- 
brandon s. allbery     [linux,solaris,freebsd,perl]       
allbery at kf8nh.com
system administrator  [openafs,heimdal,too many hats]   
allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon university       
KF8NH