port upgrade does not work correctly on current pseudo-port

[raimue@…]

Instead of taking the actual porturl, macports::upgrade searches for the port in the tree which makes the behavior totally unexpected when using the current pseudo-port.

Imagine you got some directory with a Portfile outside of your ports tree which has the same name as a port in the tree. Then run port upgrade in this directory, and not the port from this directory is build and installed, but the one from the tree. This is absolutely not expected behavior.

I think macports::upgrade should take a porturl instead of the name of a port.

[toby@…]

Milestone MacPorts base bugs deleted