Re: Problems with 'port upgrade' in DP 1.32

>On Aug 30, 2006, at 5:53 AM, Artemio Gonzalez Lopez wrote:
>>After updating (via port selfupdate) to DP 1.32, I tried to upgrade 
>>all my active ports in need of upgrading as I always do with
>>
>>port -vuf upgrade active
>
>you want port upgrade outdated
>
>(port upgrade active with -f will force it to upgrade all your 
>installed ports and all their dependencies, iirc).
>
>>P.S. On a totally unrelated matter, 'port installed foo' gives this 
>>apparently wrong answer if port foo is not installed:
>>
>>Port foo is not installed.
>>No ports are installed.
>>
>>What gives???
>
>that looks like a bug :)
>--
>Daniel J. Luke


I understand that a

sudo port upgrade outdated

will upgrade those ports which have new versions, eg going from php4 
4.4.2 to php4 4.4.4 or whatever.

But when a dependent port gets updated, eg openssl or something, do 
you have to rebuild php4 to get it to use the newly upgraded openssl, 
and with what port command? php4 isn't necessarily outdated.



Similarly, if I do a (for instance)

sudo port dependents zlib

I get

openssl depends on zlib
freetype depends on zlib
freetype depends on zlib
freetype depends on zlib
openssl depends on zlib
libpng depends on zlib
libpng depends on zlib
tiff depends on zlib
ImageMagick depends on zlib
cclient depends on zlib
curl depends on zlib
php4 depends on zlib
curl depends on zlib
php4 depends on zlib
php4 depends on zlib
php4 depends on zlib


But I only have one php4 installed. Are the multiples due to having 
gone from php4 4.4.2 to 4.4.3 to 4.4.4 to 4.4.4_1 etc ? Does it 
matter having all these multiple depends? How do I clean it up?



Mark