GNOME Bugzilla – Bug 747531
Show compatibility info on installed extensions list
Last modified: 2018-02-01 15:47:11 UTC
A frequent refrain I hear is: "I love GNOME 3, as long as I have my extensions installed. Can't live with it otherwise!" (Curiously, their list of extensions rarely overlaps the ones *I* feel I can't live without, which I guess goes to validate the idea of extensions overall.) Anyway, I'm planning on updating my desktop to 3.16, and am worried about compatibility of my "personally-vital" extensions. I know that the main list at https://extensions.gnome.org/ has knowledge of extension compatibility, because it can filter on it. It would be nice if the https://extensions.gnome.org/local/ page could also have some option to show which of my currently-installed extensions will be compatible with a _newer_ version. That way, I can check for updates, contact the upstream author, or even make a patch myself before taking the plunge (and possibly coming out the other side very grumbly).
*** Bug 667644 has been marked as a duplicate of this bug. ***
As a starting point the Installed extensions page should show the version information displayed for every installed extension. As a second step some drop-down list could be shown with the available versions, possibly grouped by desktop versions. Something like: * 3.8 6.0-11.9 * 3.10 8.5-11.9 * 3.12 9.6-13.1 (or maybe the other way around, I am not sure) This drop-down list could be used to get information and as well to navigate to a list of the versions of the given extension. The installed extensions' version number is really obscured currently but is really vital. Actually I can't really tell how to obtain it, as the Tweaks app and the Installed extensions page hides this info as well. If I'm corretct the version compatibility information is already available, so only some kind of presentations has to be implemented.
Created attachment 367761 [details] Shell versions list Shell versions list is added as part of bug 666632
*** This bug has been marked as a duplicate of bug 666632 ***