running port upgrade outdated installs the port in the current directory

[skymoo (Adam Mercer)]

I was upgrading outdated ports on my system and I noticed the following strange behaviour, if you run "port upgraded outdated" in a directory that contains a Portfile that is not installed, port upgrade outdated will install that port:

[ram@skymoo ~]$ port installed p7zip
None of the specified ports are installed.
[ram@skymoo ~]$ cd `port dir p7zip`
[ram@skymoo p7zip]$ sudo port upgrade outdated
--->  Fetching p7zip
--->  Attempting to fetch p7zip_4.57_src_all.tar.bz2 from http://downloads.sourceforge.net/p7zip
--->  Verifying checksum(s) for p7zip
--->  Extracting p7zip
--->  Applying patches to p7zip
--->  Configuring p7zip
--->  Building p7zip with target all
--->  Staging p7zip into destroot
--->  Installing p7zip 4.57_1
--->  Activating p7zip 4.57_1
--->  Cleaning p7zip
[ram@skymoo p7zip]$ 

[jmroot (Joshua Root)]

Can't reproduce this with current trunk. I get "Error: No ports found". Does the set of outdated ports have to be non-empty for this to happen?

[jmroot (Joshua Root)]

(Oops, darn autocomplete...)

[raimue (Rainer Müller)]

I already fixed this in trunk with r34546.

The behavior was that if outdated did not expand to any ports, it used the current pseudo-port instead. Now it prints just a message that no ports were given.

[tobypeterson]

Milestone MacPorts base bugs deleted