| 1 |
Ühel kenal päeval, T, 30.05.2017 kell 10:27, kirjutas Raffaele Belardi: |
| 2 |
> I have Seamonkey and the default Gnome browser (epiphany) installed, |
| 3 |
> none of which seems to be compatible with the Gnome shell extensions |
| 4 |
> plugin system. |
| 5 |
|
| 6 |
gnome-base/gnome-shell[nsplugin] ought to still work for those. |
| 7 |
|
| 8 |
> Is there an alternative way to install shell extensions? Possibly by |
| 9 |
> customizing the gnome-shell-extensions package? |
| 10 |
|
| 11 |
There are various ways: |
| 12 |
|
| 13 |
* https://extensions.gnome.org/ combined with either |
| 14 |
chrome-gnome-shell + browser plugin (it should auto-install with |
| 15 |
chrome/chromium or pop up a notification on the website with a link to |
| 16 |
the plugin); or gnome-shell[nsplugin] |
| 17 |
** Note that chrome-gnome-shell, contrary to what the name makes one |
| 18 |
possibly think, is also meant to be used with modern Firefox[1] and |
| 19 |
various other browsers that support the new-ish WebExtensions |
| 20 |
standard[2] (draft). |
| 21 |
** With chrome-gnome-shell you'd also get notifications of outdated |
| 22 |
extensions with newer versions available and to easily update them |
| 23 |
(basically avoiding having to go check on extensions.gnome.org |
| 24 |
Installed extensions tab if there are newer versions) |
| 25 |
|
| 26 |
* Installing via a system package (gnome-shell-extensions is just one |
| 27 |
such a package, there are others, mostly package name starts with |
| 28 |
"gnome-shell-extensions"), which makes it managed by package manager |
| 29 |
and be available for enabling for all users, or be default enabled for |
| 30 |
all users |
| 31 |
|
| 32 |
* Installing manually in the appropriate directory as discussed already |
| 33 |
in other replies |
| 34 |
|
| 35 |
* Installing via gnome-tweak-tool somehow, looks like via pointing it |
| 36 |
at some compressed extension tarball |
| 37 |
|
| 38 |
* Installing via gnome-software (yes, we have that packaged and the |
| 39 |
extensions side of thing should work, albeit the package currently |
| 40 |
doesn't really let it be installed without all the packagekit stuff, |
| 41 |
but the extensions work even with packagekit portage integration being |
| 42 |
rather broken in my tests - it's individual enough) |
| 43 |
|
| 44 |
Mostly it all boils down to installing to the appropriate system or |
| 45 |
user directory, rest is about monitoring for updates, having shortcuts |
| 46 |
to opening the extensions settings panel, etc. |
| 47 |
|
| 48 |
|
| 49 |
1. https://developer.mozilla.org/en-US/Add-ons/WebExtensions |
| 50 |
2. https://browserext.github.io/browserext/ |
Archives