port outdated command works propely after Porticus being installed.

[Emmanuel Hainry]

Citando Kuniaki Mukai :
> 
> However I have found there is still something wrong
> with MacPorts on my mac. Here is a new log 
> of 'port outdated'.
> 
> % sudo port sync
> Password:
> % sudo port selfupdate
> 
> MacPorts base version 1.700 installed
> Downloaded MacPorts base version 1.700
> 
> The MacPorts installation is not outdated so it was not updated
> 
> ( Porticus menu item 'Self Update' being done)
> 
> % port outdated
> The following installed ports are outdated:
> bash                           4.0.0_0 < 4.0.10_0        
> mpfr                           2.4.1-p2_0 < 2.4.1-p4_0   
> 
> 
> The new log keeps  me confused. Why does 'port outdated' command work correct 
> only after selfupdating by Porticus ,  even after 'sudo port sync' or 'sudo port selfupdate.'
> 
> Kuniaki Mukai


'sync' updates the port index which means the port definitions.
'selfupdate' does 'sync' and updates macports itself (the "port"
command). None of them do upgrade the ports themselves.

So 

port sync; port outdated

will list the ports whose definitions have been updated. If you want to
upgrade those ports, you need to

port update bash

then port outdated will only list the ports for which there is still a
definition (portfile) newer than what you have installed.

To sum up, there are portfile which are definitions of ports, that you
can sync with the 'sync' command; and there are softwares themselves
(port installed will list what you have installed, port outdated what
you can upgrade).

Porticus does nothing else than using those commands.

Best,

Emmanuel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090311/009824ce/attachment.bin>