GNOME Bugzilla – Bug 666632
Force download of an extension
Last modified: 2018-02-01 15:47:11 UTC
For example, I want to test an incompatible extension, or make another extension by code of some extensions or make it compatible with my own version or ... There isn't an option to "Force Install" or "Download" an extension, and it's useful for developers and testers. Something like AMO's website!
(In reply to comment #0) > For example, I want to test an incompatible extension You cannot do so. The Shell will flat-out reject any extension incompatible with it. I may provide an option in the future to download as a .zip file, but I would like a designer to look at the current extensions page and clean it up.
Thanks a lot. I know the Shell will reject it, but "force install" is useful when I need it, when it become update and compatible with my version! It means something like "Subscribe" :-D But, "download" is very useful for developers (what I need now!) and I must do a lot of works to find where the files are on your server to download an extension! (If you know, and if it is possible, please say to me :-) ) PS: what do you mean by a designer? a graphical designer or a web designer who code HTML/CSS/JS? We have some, if it is needed :-P
This blocks testing/contributions to extensions, increasing severity to major. For extensions without a (working) link to a homepage/repository, contributors cannot fix an incompatible extension to work with the most recent GNOME Shell version. Looking at the source code, it is possible to download extensions manually from https://extensions.gnome.org/download-extension/$UUID.shell-extension.zip?version_tag=latest However, that's not exactly discoverable.
(In reply to comment #2) > Thanks a lot. > > I know the Shell will reject it, but "force install" is useful when I need it, > when it become update and compatible with my version! It means something like > "Subscribe" :-D This opens a big can of worms. I'll certainly have to think about multiversion in the future when I hack on auto-updating.
Why is the download button still missing? I want to learn how to write an extension and want just look how others have done this. I search for extensions which may use something I plan to use, but not all are compatible with my version of gnome-shell. You are giving me a hard time, getting the code.
I agree that extensions should be downloadable without requiring compatibility. In addition to learning how to write an extension, often a minor tweak will make an extension work. And sometimes the compatibility engine incorrectly rejects an extension. (Both cases occur with mozilla extensions. During an upgrade, often the compatibility engine rejects an installed extension, which nevertheless continues to work entirely correctly afterwards.) Note that some users will prefer to have a downloaded installable copy on their machine, to facilitate reinstallation when reliable internet access isn't available. (For example, when on voyage.) Although I do agree that forced install is not generally a good idea.
*** Bug 700031 has been marked as a duplicate of this bug. ***
Created attachment 269129 [details] User script to add download links to extensions.gnome.org For people who want to have direct download links on e.g.o, here's a user script that adds them. In Firefox (tested on), you'll need Greasemonkey or another user script extension; Chromium/Chrome should be able to handle it directly.
I'd strongly argue that *requiring* a browser plugin to download/manage extensions is a bad idea: * Increases the browser attack surface area permanently across all websites for a very limited use - this proliferation of plugins of often minimal value has led to a history of exploitable vulnerabilities - plugins generally are a key target for drive-by attacks (see for example Java...) As it stands, any flaw in the plugin would be exploitable from any site, unless (using the Fedora/Firefox default as an example at least) the user explicitly changes the plugin to 'Ask to activate'. This mitigates some of the security issue, but requires browser-specific functionality (I'm pretty sure Gnome Web doesn't have that fine-grained capability for example). * Doesn't provide any additional functionality - convenience yes, but it should be the user's choice whether to run a plugin on this basis. Direct links could be displayed only when the plugin is disabled if desired, maybe with a FAQ item on this, improving the experience for people choosing not to run the plugin. * Requires web access on the target machine to install extensions, and (save for the existence of Gnome Tweak Tool) would require web access in order to configure/disable extensions. Plane/train travel = lost functionality. Website down = lost functionality. Incidentally, another application that requires the use of a website to configure system software, an approach infamous for being unpopular with many users, is Flash... ;)
*** Bug 768472 has been marked as a duplicate of this bug. ***
*** Bug 739297 has been marked as a duplicate of this bug. ***
*** Bug 741950 has been marked as a duplicate of this bug. ***
Yuri: Any news to share? (Asking as you assigned this task to yourself.)
It's in my TODO. I'm a bit busy last monthes and will be busy for a month
Download options now available at extension details page.
*** Bug 747531 has been marked as a duplicate of this bug. ***