"port upgrade all" should be diagnosed as an error

[Dave@…]

If the command is 'port upgrade all', the port command should look to see if there are any members of 'all' that are not installed, and diagnose this usage as incorrect, AND suggest that perhaps the user meant 'port upgrade oudated'.

You may find this useful ​http://developer.apple.com/documentation/userexperience/Conceptual/AppleHIGuidelines/XHIGWindows/XHIGWindows.html#//apple_ref/doc/uid/20000961-TPXREF23

See also #19428

[raimue (Rainer Müller)]

We never instruct to use port upgrade all, so I don't see why you would do this at all. The error message that the requested port is not installed is clear enough, isn't it?

[Dave@…]

Replying to raimue@…:

We never instruct to use port upgrade all, so I don't see why you would do this at all. The error message that the requested port is not installed is clear enough, isn't it?

It's a reasonable mistake, I think.

[banshee@…]

Speaking as a new user, it was completely obvious to me that 'port upgrade all' would mean to upgrade everything I've got installed. It's exactly like "apt-get upgrade all" . An error message explaining that "all" means something else would have been very helpful.

The current errors aren't useful at all. I asked for "all" and it starts complaining about software that I've never installed. It makes sense, eventually, after you find out that "all" doesn't mean what you think it does.

[ryandesign (Ryan Carsten Schmidt)]

The ChangeLog for MacPorts 1.7.1 says Joshua fixed this in r46052. Are you still seeing a problem with MacPorts 1.7.1? I get, e.g.

$ port installed zope
None of the specified ports are installed.
$ port upgrade zope
Error: zope is not installed
$ 

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

Joshua fixed this in r46052.

That is to say, Joshua fixed it in 1.7.1 so that "port upgrade all" no longer tries to install all ports (!). But if the request is to provide a better error message than

$ port upgrade all
Error: 2Pong is not installed
$

then that request is still outstanding.

[raimue (Rainer Müller)]

The original problem seems to have been fixed a long time ago. It is unclear to me what else we could do here. If there is still a problem, please open a new ticket.