[MacPorts] #63438: port checksum outdated doesn't work: version ... is not available (was: base 2.7.1: port checksum outdated chokes)

[MacPorts]

#63438: port checksum outdated doesn't work: version ... is not available
----------------------------+--------------------
  Reporter:  jmarshallidau  |      Owner:  (none)
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  base           |    Version:  2.7.1
Resolution:                 |   Keywords:
      Port:                 |
----------------------------+--------------------
Changes (by ryandesign):

 * cc: jmroot (added)


Comment:

 Well, the change was intentional, though I certainly didn't anticipate
 that anybody would run `port checksum outdated` or that the change would
 have this effect in that case. You can read about the change in #60454.

 The change was that port version numbers may no longer be specified when
 it is inappropriate to do so. Originally the change only applied to the
 "install" action. It was then changed to apply to all actions except for
 "clean". The "outdated" pseudoport expands to a list of port names and
 their currently-installed version/revision/variants, hence the problem you
 experienced. We could also allow it in the "checksum" action, however if
 you expect `port checksum outdated` to work, you might also expect `port
 fetch outdated`, `port patch outdated`, `port configure outdated`, `port
 build outdated`, and `port destroot outdated` to work too, and they also
 don't anymore since MacPorts 2.7.0. (`port upgrade outdated` still works,
 as we would want it to, though I'm unclear on how that's being allowed
 through.) Should we go back to just prohibiting version numbers in the
 "install" action?

-- 
Ticket URL: <https://trac.macports.org/ticket/63438#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS