On Fri, Apr 4, 2014 at 2:34 PM, Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/03/2014 01:10 PM, drago01 wrote: >> On Thu, Apr 3, 2014 at 5:43 PM, Matthew Miller >> <mattdm@xxxxxxxxxxxxxxxxx> 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? >> >> How about this: >> https://extensions.gnome.org/extension/797/extension-update-notifier/ >> >> > ? >> >> Testing welcome I just wrote it so got very limited testing so >> far. >> > > How does this play with extensions that are packaged in RPMs (such as > the extensions that come with GNOME Classic)? I'm guessing it would > encourage you to install the local copy in your home directory, which > would diverge from the system copy. Good point, updated a new version that ignores system wide extensions. -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
