GNOME Bugzilla – Bug 673610
gnome-shell-calendar-server: deal with Evolution's move to GSettings
Last modified: 2012-04-19 00:15:20 UTC
Somehow nobody has noticed that the configuration we were looking at for enabled calendars is no longer at the location where we were looking.
Created attachment 211435 [details] [review] gnome-shell-calender-server: fix debug prints Several debug prints not normally compiled were referencing enumeration values that have since been renamed.
Created attachment 211436 [details] [review] gnome-shell-calendar-server: deal with Evolution's move to GSettings Evolution now stores its selected calendars and tasks in GSettings, not in GConf. If we don't look at the new location, then we'll not pick up newly added and enabled calendars, making the calendar effectively not work for new installs.
*** Bug 673637 has been marked as a duplicate of this bug. ***
Review of attachment 211435 [details] [review]: Sure.
*** Bug 673672 has been marked as a duplicate of this bug. ***
Review of attachment 211436 [details] [review]: ugh. I'm disappointed that 1) it's half GConf and half GSettings, and 2) e-d-s doesn't handle this for us, but well... Otherwise, this looks fine.
can this patch land in master before 3.4.1?
Attachment 211435 [details] pushed as 0e8fd45 - gnome-shell-calender-server: fix debug prints Attachment 211436 [details] pushed as 5046938 - gnome-shell-calendar-server: deal with Evolution's move to GSettings
(In reply to comment #6) > ugh. I'm disappointed that 1) it's half GConf and half GSettings, and 2) e-d-s > doesn't handle this for us, but well... For the record I'm working on the remaining GConf keys, but it's taking a long time to complete. The horrible XML account blobs that Evolution keeps in GConf are not destined for GSettings. Instead they're destined for a whole new account format and a whole new API. Details are here if you're curious... http://live.gnome.org/Evolution/ESourceFileFormat I shall help with the gnome-shell-calendar-server porting as soon as this lands.
*** Bug 673474 has been marked as a duplicate of this bug. ***
*** Bug 674224 has been marked as a duplicate of this bug. ***