After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660460 - don't use gconf
don't use gconf
Status: RESOLVED DUPLICATE of bug 647909
Product: folks
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: Unset
Assigned To: folks-maint
folks-maint
Depends on:
Blocks: 622558
 
 
Reported: 2011-09-29 12:49 UTC by Matthias Clasen
Modified: 2011-09-29 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2011-09-29 12:49:37 UTC 
folks seems to link against gconf.

There's a single gconf key referenced in the code, and it doesn't even have a schema.

If the key is necessary, you should use gsettings / dconf. But considering it is just a single key, maybe you can get by without it ?
Comment 1 Travis Reitter 2011-09-29 14:33:32 UTC 
(In reply to comment #0)
> folks seems to link against gconf.
> 
> There's a single gconf key referenced in the code, and it doesn't even have a
> schema.
> 
> If the key is necessary, you should use gsettings / dconf. But considering it
> is just a single key, maybe you can get by without it ?

The main reason we used GConf instead of GSettings to start with is that MeeGo didn't support GSettings.

At any rate, we're planning to move onto GSettings soon.

*** This bug has been marked as a duplicate of bug 647909 ***