port outdated command works propely after Porticus being installed.

[William Davis]

On Mar 11, 2009, at 1:32 AM, Kuniaki Mukai wrote:

>
> Here is a command line log of MacPorts.
>
> % port outdated
> The following installed ports are outdated:
> mpfr                           2.4.1-p2_0 < 2.4.1-p4_0
> % sudo port selfupdate
> Password:
>
> MacPorts base version 1.700 installed
> Downloaded MacPorts base version 1.700
>
> The MacPorts installation is not outdated so it was not updated
> % sudo port sync
>
> (Launch Porticus and do the menu item  selfupdate, which
> shows only bash and graphviz are outdated. )
>
> % port outdated
> The following installed ports are outdated:
> bash                           4.0.0_0 < 4.0.10_0
> graphviz                       2.22.0_0 < 2.22.1_0
> mpfr                           2.4.1-p2_0 < 2.4.1-p4_0
> %
>
> It seems that this log still suggests that 'port outdated' command
> works correct only after Porticus selfupdate menu being done,
> as I suspect.
>
>
> K. Mukai
>


You need to do "sudo port -d selfupdate" before
port outdated not after.

You see "selfupdate" is what causes your own port file index to get  
updated. Port didnt know about bash and graphviz because your index  
was not "up-to-date" when up gave the "port outdated" command. All  
porticus did was give port the same selfupdate command you could have  
given on the command line before you gave the port outdated command.

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non