| 3 | | 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? |
| | 3 | 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 then you might expect `port fetch outdated`, `port patch outdated`, `port configure outdated`, `port build outdated`, `port test 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? |
