Changes between Initial Version and Version 1 of Ticket #68820, comment 4
- Timestamp:
- Dec 5, 2023, 6:39:47 PM (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #68820, comment 4
initial v1 1 1 Replying to [comment:3 fhgwright]: 2 > Replying to [comment:2 neverpanic]:3 > > Is there a chance that you had both versions installed but one of them inactive?4 >5 > Bingo. I still had 3.1.4_1 installed, and it was probably from a build with the epoch bumped. After rolling it back to 3.1.4_0, gojng forward from there worked as intended.6 >7 2 > I suspect that this related to the "held back hack". It seems that when the active version isn't the latest version, then "upgrade outdated" leaves it alone on the theory that if the user has an older version active, there's probably a reason for that and it should be left alone. That's reasonable in principle, but I think it would be more appropriate to apply that logic to the definition of "outdated" rather than to the action of "upgrade". 8 3 … … 11 6 12 7 13 > I see five possible mutually exclusive and exhaustive classifications for the installation status of a given port on a given system:14 >15 > Current: the active instance is the newest installed version, and no newer version is available.16 >17 > Outdated: the active instance is the newest installed version, and a newer version is available.18 >19 > Held-back: the active instance is not the newest installed version.20 >21 > Inactive: at least one instance is installed, but none is active.22 >23 > Uninstalled: no instances are installed.24 >25 8 > With that, "upgrade" should mean installing and activating the current version if it's newer than the active version, preserving variants to the extent possible, where "installing" might be a NOP if the relevant version/variants is already installed. No need for a "held back hack" in "upgrade" when "upgrade outdated" uses the above definition of "outdated" 26 9 27 I don't think we have hold-back functionality implemented in upgrade. It's simply that outdated does not include such p rots. Check with `port installed outdated`.10 I don't think we have hold-back functionality implemented in upgrade. It's simply that outdated does not include such ports. Check with `port installed outdated`. 28 11 29 12