'port outdated' doesn't match actual ports to be upgraded with 'port upgrade outdated'.

[bettybronner@…]

Running 'port outdated' and 'port list outdated' should show every port that will be upgraded when 'port upgrade outdated' is run. At least that is the most intuitive behavior.

See example below:

...
The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
bash-3.2# port outdated
The following installed ports are outdated:
pkgconfig                      0.25_2 < 0.26_0
freetype                       2.4.4_0 < 2.4.5_0
sqlite3                        3.7.6_0 < 3.7.7_0
curl-ca-bundle                 7.21.6_0 < 7.21.7_0
curl                           7.21.6_0 < 7.21.7_0
apr                            1.4.5_0 < 1.4.5_1
bash-3.2# port upgrade outdated
--->  Computing dependencies for glib2
--->  Fetching glib2
--->  Attempting to fetch glib-2.28.8.tar.bz2 from http://distfiles.macports.org/glib2
--->  Verifying checksum(s) for glib2
--->  Extracting glib2
--->  Applying patches to glib2
--->  Configuring glib2
^C
bash-3.2# port list outdated
pkgconfig                      @0.26           devel/pkgconfig
freetype                       @2.4.5          print/freetype
sqlite3                        @3.7.7          databases/sqlite3
curl-ca-bundle                 @7.21.7         net/curl-ca-bundle
curl                           @7.21.7         net/curl
apr                            @1.4.5          devel/apr
bash-3.2#

I stopped this upgrade midstream because suddenly 'glib2' was being upgraded when it wasn't listed and I didn't want something more critical being upgraded that wasn't listed in the 'outdated' set.

[danielluke (Daniel J. Luke)]

port list outdated probably doesn't do what you expect.

It looks like glib2 was added as a dependency for pkgconfig when it was upgraded to 0.26, and so needs to be installed before the newer pkgconfig can be installed.

[bettybronner@…]

Replying to dluke@…:

port list outdated probably doesn't do what you expect.

It looks like glib2 was added as a dependency for pkgconfig when it was upgraded to 0.26, and so needs to be installed before the newer pkgconfig can be installed.

Okay, well then there should be an option to do what most people probably expect.

[danielluke (Daniel J. Luke)]

Replying to bettybronner@…:

Okay, well then there should be an option to do what most people probably expect.

most people expect port upgrade outdated to install the newest versions of all of the ports in port outdated ... most people also don't expect port to install non-functional versions of ports. In this case, in order to install the newest version of pkgconfig, it had to install glib2.

[bettybronner@…]

Replying to dluke@…:

Replying to bettybronner@…:

Okay, well then there should be an option to do what most people probably expect.

most people expect port upgrade outdated to install the newest versions of all of the ports in port outdated ... most people also don't expect port to install non-functional versions of ports. In this case, in order to install the newest version of pkgconfig, it had to install glib2.

Of course. I'm merely pointing out that 'glib2' should be listed as a port that will be installed. Users don't want surprises to suddenly show up.

[jmroot (Joshua Root)]

There's the dry-run option -y for finding out what a command will do.