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 781001 - Provide a way for a downstream to be able to block some extensions
Provide a way for a downstream to be able to block some extensions
Product: gnome-software
Classification: Applications
Component: General
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Reported: 2017-04-06 23:48 UTC by Ryan Lerch
Modified: 2018-01-24 17:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Ryan Lerch 2017-04-06 23:48:45 UTC
Currently, there is no way of curating / blocking what extensions show up in GNOME Software from the gnome extenstions website.

For example, having this extension showing up in GNOME Software in Fedora is probably not very useful:
Comment 1 Christian Stadelmann 2017-04-12 11:37:19 UTC
I think a better solution would be to add a "required dependencies" mechanism to the gnome-shell extensions metadata, which the shell or gnome-software can check before installing. This would also resolve issues with many other gnome-shell extensions requiring other packages to be installed. Some examples: requires gtop (Version 2) requires lm-sensors

Exaile, a music player written in Python + GObject, has implemented this in a nice way. See field "RequiredModules":
Code implementation:
Plugin metadata files:
Comment 2 GNOME Infrastructure Team 2018-01-24 17:32:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: