After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 667644 - need info about gnome-shell version compatibility for every extension
need info about gnome-shell version compatibility for every extension
Status: RESOLVED DUPLICATE of bug 747531
Product: website
Classification: Infrastructure
Component: extensions.gnome.org
current
Other All
: Normal normal
: ---
Assigned To: Shell extensions maintainer(s)
Shell extensions maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-01-10 17:48 UTC by Roman Polach
Modified: 2015-07-02 18:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Roman Polach 2012-01-10 17:48:20 UTC
It would be very helpful if every extension page
have a info about gnome-shell version compatibility
for this specific extension.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-01-12 00:46:26 UTC
What exactly do you want to know? If the extension is not compatible and your Shell version is too old, it will tell you what version to upgrade to.
Comment 2 Roman Polach 2012-01-12 09:41:46 UTC
Well I would like to know the compatibility version before.
I am going to switch distro, and considering Mint, Fedora...
Different distros have different Gnome version. I have clear
idea what set of extensions from extensions.gnome.org I would
like to use. And it is important to me to know whether these
extensions would be available in specific distro...
So if, for example, most extensions support only 3.0 and not
newer version of Gnome-shell I would not consider distro with
newer Gnome...
Comment 3 Jasper St. Pierre (not reading bugmail) 2012-01-12 15:07:42 UTC
No extensions on extensions.gnome.org support 3.0. All of them support at least 3.2.
Comment 4 Roman Polach 2012-01-13 09:10:12 UTC
Ok, the same question is between 3.2, 3.4 and on...
Comment 5 Alexandre Franke 2015-07-02 18:43:09 UTC

*** This bug has been marked as a duplicate of bug 747531 ***