jarabe, extensions - remove GConf compatibility

[quozl]

GConf compatibility support in Sugar allowed activities to read or be notified of changes to age, gender, nick, user colour, collaboration server, backup server, or automatic power management. Redundant code updated GConf values at the same time as updates to Gio.Settings values.

Remove GConf from Sugar;

• remove the autoconf rules,

• remove the Makefile rules,

• remove the schema conversion for upgrades from GTK+ 2 Sugar,

• remove the gsettings-migrated setting key,

• remove the GConf schema,

• remove redundant code for GConf value updates,

• remove migration from GConf to Gio.Settings.

Warning: may break some activities. May cause default values to be used, traceback, or fail to start for any activity using the removed GConf schema to read the removed configuration values for; age, gender, nick, user colour, collaboration server, backup server, and automatic power management. Fix GTK+ 2 activities by porting to GTK+ 3 and Gio.Settings. Fix GTK+ 3 activities by porting from GConf to Gio.Settings.

Tested on Ubuntu 16.04.

[tony37]

Another make-work project for developers. The best solution would be to return to the config file in /home/olpc/.sugar/defaults. That has no dependency on upstream and is therefore immune from these diktats. Tony

…

On Monday, 26 March, 2018 05:59 AM, James Cameron wrote: * removes GConf dependency, * breaks GTK+ 2 activities; this version of Sugar will cause traceback and fail to start for any activity using a GConf schema to read configuration values for; age, gender, nick, user colour, collaboration server, backup server, automatic power management. Untested. ------------------------------------------------------------------------ You can view, comment on, or merge this pull request online at: #792 Commit Summary * jarabe, extensions - remove GConf compatibility File Changes * *M* configure.ac <https://github.com/sugarlabs/sugar/pull/792/files#diff-0> (11) * *M* data/Makefile.am <https://github.com/sugarlabs/sugar/pull/792/files#diff-1> (7) * *M* data/org.sugarlabs.gschema.xml <https://github.com/sugarlabs/sugar/pull/792/files#diff-2> (5) * *D* data/sugar-schemas.convert <https://github.com/sugarlabs/sugar/pull/792/files#diff-3> (69) * *D* data/sugar.schemas.in <https://github.com/sugarlabs/sugar/pull/792/files#diff-4> (491) * *M* extensions/cpsection/aboutme/model.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-5> (15) * *M* extensions/cpsection/network/model.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-6> (11) * *M* extensions/cpsection/power/model.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-7> (5) * *M* src/jarabe/desktop/schoolserver.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-8> (7) * *M* src/jarabe/intro/__init__.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-9> (6) * *M* src/jarabe/intro/agepicker.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-10> (5) * *M* src/jarabe/intro/genderpicker.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-11> (6) * *M* src/jarabe/intro/window.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-12> (10) * *M* src/jarabe/main.py <https://github.com/sugarlabs/sugar/pull/792/files#diff-13> (106) Patch Links: * https://github.com/sugarlabs/sugar/pull/792.patch * https://github.com/sugarlabs/sugar/pull/792.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#792>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAULkvLKzn1-QCfA90dFbQ6N1b6NGHNyks5tiGeXgaJpZM4S6fTR>.

[quozl]

Returning to a defaults file would break compatibility with settings made by builders or shell scripts. It would also lose locking, and settings change notification.

We could also avoid GTK+ and use something more stable like X or Qt, but such a port would be a huge make-work. With the withdrawal of GTK+ 2 we lose the use of many abandoned activities.