Ports, pkg's confusion on upgrades...

[Karl Pielorz]

Hi,

We have a number of 10.x systems now - where we install packages (aka pkg 
install) some components, but other components we build from ports (as we 
need to add / remove options that the package gives you no choice over).

Initially 'pkg upgrade' wanted to replace the port versions with pkg 
versions (which include options we don't want, and would have pulled in a 
lot of other dependencies).

I seem to have fixed this by 'locking' them (i.e. pkg lock) - pkg upgrade 
doesn't want to touch them now, which is good.

But, 'pkg upgrade' still wants to pull in more packages than are installed 
- i.e. 'pkg upgrade' shows entries under "to be INSTALLED" as well as "to 
be UPGRADED".

'pkg info -a -d' displays the dependencies of all installed packages (none 
of which depend on the package it wants to install) - but I can't seem to 
find any way to get 'pkg upgrade' to tell me why it wants to install a new 
package (i.e. which *upgrade* is it doing that now requires the "to be 
INSTALLED" packages?)


-Karl