> gsettings set org.gnome.shell disable-extension-version-validation false

Obviously I mean if you set it on true :)


On Thu, Apr 3, 2014 at 8:07 PM, alex diavatis <alexis.diavatis@gmail.com> wrote:
> gsettings set org.gnome.shell disable-extension-version-validation false

If you do this, then extension.gnome.org will let you to install extensions for every version.
So you will definitely get broken extensions. 
That isn't the case for now, but it is a known bug, that may resolve at some point. 

Other than this it also creates issues in Tweak Tool, 
that people use a lot for managing their extensions. For example Tweak Tool won't show incompatibilities.

- alex 


On Thu, Apr 3, 2014 at 8:03 PM, Matthias Clasen <mclasen@redhat.com> wrote:
On Thu, 2014-04-03 at 11:43 -0400, Matthew Miller wrote:
> On Thu, Apr 03, 2014 at 04:24:26PM +0100, Matthew Garrett wrote:
> > > I've had a pretty good experience here this time around. Almost everything
> > > worked when I told it to not do the check, and others were updated. Also,
> > > when I look at https://extensions.gnome.org/ sorted by popularity, _most_ of
> > > the top ones are already updated. I'd like to see an effort to get the
> > > remaining few that are on the top N pages updated, and then I'd be pretty
> > > comfortable recommending this as an F20 update.
> > But actually updating the ones that don't work is a manual process on
> > the part of the user, right?
>
> Yeah -- see devel list post. I forgot about that because I do that manual
> process fairly often.
>
> I kind of feel like this is, therefore, a showstopper. Any suggestions for
> unstopping it, anyone?

It would be good to know if there are widely-used extensions that will
not continue to work when you install 3.12 and then

gsettings set org.gnome.shell disable-extension-version-validation false

The one example I have seen mentioned so far is
gnome-shell-extension-fedmsg