Opened 6 years ago
#57950 new enhancement
port selfupdate gives the impression of doing work in the wrong order
Reported by: | saagarjha (Saagar Jha) | Owned by: | |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | base | Version: | 2.5.4 |
Keywords: | Cc: | ||
Port: |
Description
When running port selfupdate, the order in which output appears looks something like this:
$ port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.5.4 installed, MacPorts base version 2.5.4 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version
From a end-user perspective, it seems odd that MacPorts needed to update the ports tree before telling me that I have the latest version, considering that it tells me the version I have before this (which should be enough for it to determine this?). I'd expect the output to look like this, to match the logic operations that are being performed:
$ port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.5.4 installed, MacPorts base version 2.5.4 downloaded. ---> MacPorts base is already the latest version ---> Updating the ports tree
Looking at the source code for selfupdate, it seems that this is done mainly because it simplifies a conditional, but I see no reason why this couldn't be changed to display the messages at the logical point that they should appear.
Note: See
TracTickets for help on using
tickets.