migrate settings from GConf to GSettings on upgrade
Submitted by Adam Dingle
Assigned to Jim Nelson
Link to original bug (#717801)
Description
---- Reported by adam@yorba.org 2011-06-20 14:09:00 -0700 ----
Original Redmine bug id: 3765
Original URL: http://redmine.yorba.org/issues/3765
Searchable id: yorba-bug-3765
Original author: Adam Dingle
Original description:
migrate settings from GConf to GSettings on upgrade
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
Perhaps we can use gsettings-data-convert for this purpose:
http://developer.gnome.org/gio/stable/ch28s07.html
That would introduce a dependency on GConf, however.
Comment 2
Updated by Adam Dingle over 2 years ago
- Description updated (diff)
- Assignee changed from Lucas Beeler to Jim Nelson
Comment 3
Updated by Jonas Bushart over 2 years ago
I can write the conversion file for gsettings-data-convert if you want to choose this option.
Even if the website (http://developer.gnome.org/gio/stable/ch28s07.html) tells to set gconf as a dependency I think it is not necessary.
If there is not a gconf system then there won´t be data to migrate. The conversation file could be installed but nothing would happen.
The correct version could be already installed if gconf is installed.
If the correct version is not installed it may come with an update or it won´t come (like Ubuntu is not installing new versions of programs).
In the worst case (gconf data is lost) the user has to reconfigure the program with three simple tabs in preferences.
I think we can justify to leave out the dependency%.%
Comment 4
Updated by Jim Nelson over 2 years ago
- Status changed from Open to 5
- Resolution set to fixed
Committed in r4d039f74
Comment 5
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 3765 at http://redmine.yorba.org/show_bug.cgi?id=3765
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.11
Resolution: RESOLVED FIXED