Date
1 - 3 of 3
Add-on updater and numerical updates or downgrades
|
Dark Count
HI there.
Since the new community resources were introduced, from time to time I like to check between them. Unfortunately if I update from one, I get messages from add-on updater to the effect that updates are available comprising of prior version updates. For instance, windows apps just now told me version 22.09.1 was available and I am already running 22.10. This is not just limited to the community resources however. I had Tony's enhancements in a more recent version than what was available in the NVDA community add-ons, and each time it kept trying to down grade me. Is this a bug, or limitation on the actual numbering system. Thanks, D C |
|
|
|
Hi
toggle quoted message
Show quoted text
This is not a bug. Versions are strings, so Python (as called by Add-on Updater) performs a string comparison when looking for updates. Due to subtleties with string comparisons and sorting order, version 9.0 is seen as newer than 10.0 (ASCII values). The add-on store repository (under development by NV Access) resolves this by storing version as a string and as major/minor/revision set by add-on authors (in major.minor.revision scheme, Windows App Essentials 22.10 would be 22.10.0). The obvious problem is how to represent development releases - using a string makes more sense whereas it becomes harder to define major.minor.revision representation (currently I'm thinking about using yymm.date.revision or a higher number in the revision field to represent development releases i.e. 2209.26.0 or 22.09.2600 to represent September 26th dev build). The underlying problem is repository maintenance. As more repos are added to Add-on Updater, it becomes important for repo maintainers to keep add-on updates metadata up to date. This is another reason for NV Access to develop the add-on store repository so all community add-ons published so far (including ones not on community add-ons website yet) can be represented in metadata form under one roof. As for community add-ons website repo, it is not enough to get updates reviewed and approved - they must be merged into add-on files repository which hasn't happened yet for some add-ons, including some of Tony's add-ons (Tony released them earlier this year at a time when he had time to update them, and he changed last tested version to 2022.1 knowing that he may not be able to update this field by the time NVDA 2022.1 beta came out). Because these add-on releases were released before 2022.1 beta came out, reviewers told Tony that updates could not be processed unless last tested version was changed or until the beta was published (remember that API for an NVDA release is frozen when beta 1 is published, and between the time Tony released his add-on updates and 2022.1 beta came out, changes were made to NVDA API, including a last minute change to support old and new control types syntax). Cheers, Joseph -----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Dark Count Sent: Monday, September 26, 2022 11:57 AM To: nvda-addons@nvda-addons.groups.io Subject: [nvda-addons] Add-on updater and numerical updates or downgrades HI there. Since the new community resources were introduced, from time to time I like to check between them. Unfortunately if I update from one, I get messages from add-on updater to the effect that updates are available comprising of prior version updates. For instance, windows apps just now told me version 22.09.1 was available and I am already running 22.10. This is not just limited to the community resources however. I had Tony's enhancements in a more recent version than what was available in the NVDA community add-ons, and each time it kept trying to down grade me. Is this a bug, or limitation on the actual numbering system. Thanks, D C |
|
|
|
Brian's Mail list account
Yes I saw this happen as well the other day, but it payees tope vigilant and read what is being presented as if you download from a link to github from the author, say on this list, you are, while the admin is done to get it on the web site, going to be offered the older version.
toggle quoted message
Show quoted text
Brian -- bglists@... Sent via blueyonder.(Virgin media) Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...> To: <nvda-addons@nvda-addons.groups.io> Sent: Monday, September 26, 2022 8:24 PM Subject: Re: [nvda-addons] Add-on updater and numerical updates or downgrades Hi This is not a bug. Versions are strings, so Python (as called by Add-on Updater) performs a string comparison when looking for updates. Due to subtleties with string comparisons and sorting order, version 9.0 is seen as newer than 10.0 (ASCII values). The add-on store repository (under development by NV Access) resolves this by storing version as a string and as major/minor/revision set by add-on authors (in major.minor.revision scheme, Windows App Essentials 22.10 would be 22.10.0). The obvious problem is how to represent development releases - using a string makes more sense whereas it becomes harder to define major.minor.revision representation (currently I'm thinking about using yymm.date.revision or a higher number in the revision field to represent development releases i.e. 2209.26.0 or 22.09.2600 to represent September 26th dev build). The underlying problem is repository maintenance. As more repos are added to Add-on Updater, it becomes important for repo maintainers to keep add-on updates metadata up to date. This is another reason for NV Access to develop the add-on store repository so all community add-ons published so far (including ones not on community add-ons website yet) can be represented in metadata form under one roof. As for community add-ons website repo, it is not enough to get updates reviewed and approved - they must be merged into add-on files repository which hasn't happened yet for some add-ons, including some of Tony's add-ons (Tony released them earlier this year at a time when he had time to update them, and he changed last tested version to 2022.1 knowing that he may not be able to update this field by the time NVDA 2022.1 beta came out). Because these add-on releases were released before 2022.1 beta came out, reviewers told Tony that updates could not be processed unless last tested version was changed or until the beta was published (remember that API for an NVDA release is frozen when beta 1 is published, and between the time Tony released his add-on updates and 2022.1 beta came out, changes were made to NVDA API, including a last minute change to support old and new control types syntax). Cheers, Joseph -----Original Message----- From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Dark Count Sent: Monday, September 26, 2022 11:57 AM To: nvda-addons@nvda-addons.groups.io Subject: [nvda-addons] Add-on updater and numerical updates or downgrades HI there. Since the new community resources were introduced, from time to time I like to check between them. Unfortunately if I update from one, I get messages from add-on updater to the effect that updates are available comprising of prior version updates. For instance, windows apps just now told me version 22.09.1 was available and I am already running 22.10. This is not just limited to the community resources however. I had Tony's enhancements in a more recent version than what was available in the NVDA community add-ons, and each time it kept trying to down grade me. Is this a bug, or limitation on the actual numbering system. Thanks, D C |
|
|