[MacPorts] #44509: selfupdate tried to tell me to run selfupdate again

[MacPorts]

#44509: selfupdate tried to tell me to run selfupdate again
---------------------+--------------------------------
  Reporter:  dave@…  |      Owner:  macports-tickets@…
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.3.1
Resolution:          |   Keywords:  selfupdate
      Port:          |
---------------------+--------------------------------

Comment (by dave@…):

 I suppose
 {{{
 sudo /opt/local/bin/port -u upgrade outdated
 }}}
 isn't an earthshaking improvement because one could do this and walk away
 while it chugs away.
 {{{
 sudo /opt/local/bin/port selfupdate && sudo /opt/local/bin/port upgrade
 outdated
 }}}
 It's just that mental modelwise, why should anyone have to remember to do
 a selfupdate, have to make the decision "has it been long enough so I
 should do a selfupdate?", and why should anyone (other than a developer of
 the port command) have to think of selfupdate as a separate step that has
 to be run by itself?

 For that matter, why can't the server give a quick yes/no answer to the
 question "is selfupdate necessary?" so that my MacPorts client can do
 selfupdate if necessary, without undo performance penalty? If this
 performance issue could be solved, then there should be an option to tell
 MacPorts NOT to do a selfupdate, as selfupdate should be the default.

-- 
Ticket URL: <https://trac.macports.org/ticket/44509#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X