GNOME Bugzilla – Bug 644463
Extensions should be whitelisted (not blacklisted)
Last modified: 2011-05-25 21:48:04 UTC
I think it is more sensible to have system-wide extensions disabled by default (and require being white-listed) instead of the current behavior where all installed extensions are enabled until explicitly disabled. My reasons for this are * gnome-shell-extensions builds all extensions by default, the net effect being the default install changes the shell in many ways * it means that distro packers can create just one package for g-s-e and not many subpackages * it matches the behavior of gedit, etc where the -plugin package installs many plugins that are disabled by default * it more correctly meshes with the idea of user extensions (which likely would be enabled by default) So, is this a good idea? Would you take a patch that either; requires white-listing system extensions, or requires white-listing all extensions?
White listing system extensions I think is definitely a good idea; it seems likely to me that people deploying system extensions are more likely to only want them for a few users, than to have them for all. Either way of course it's just a matter of scripting gschema for users. Not a big fan of white listing all extensions, but if it makes the code a lot cleaner or something we can do it.
*** This bug has been marked as a duplicate of bug 651088 ***