GNOME Bugzilla – Bug 328762
Need to separate development gconf from stable/release gconf settings
Last modified: 2018-06-29 20:56:07 UTC
After the 2.0 release we need to make an adjustment to how we handle our gconf settings. In particular, once development has diverged at all in terms of the settings stored in gconf we need to have a way to allow someone running a development version to also run the stable version. One approach is to have two sets of gconf entries, one for the stable release track and one for the development track. The stable release track is always the same (although we might want to know what stable version was last used to allow upgrades). The dev release should allow an "import settings from previous version" option which lets you import from the previous "stable" version into the current version, but then changes should go into a new configuration database so it doesn't affect the stable version. I don't have a strong opinion about whether different stable versions need to co-exist (e.g. 2.0 and 2.2) -- so it may be reasonable to have "gnucash" and "gnucash-dev" and just be done with it.. On the other hand it might also be reasonable to allow upgrading the gconf schemas and allow 2.0 and 2.2 to coexist. I'm not sure. But we definitely need to allow 2.0 and pre-2.2-dev to co-exist and not trample each other.
-devel discussion: https://lists.gnucash.org/pipermail/gnucash-devel/2006-July/018287.html https://lists.gnucash.org/pipermail/gnucash-devel/2006-August/018300.html
Committed a variation on James Radley's patch to gnucash-devel as r15760.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=328762. Please update any external references or bookmarks.