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 528096 - GNOME should use single directory for all config settings (e.g. $HOME/.config)
GNOME should use single directory for all config settings (e.g. $HOME/.config)
Status: RESOLVED DUPLICATE of bug 518590
Product: GConf
Classification: Deprecated
Component: gconf
2.22.x
Other All
: Normal enhancement
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-14 19:38 UTC by Lewis Thompson
Modified: 2009-03-01 19:03 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Lewis Thompson 2008-04-14 19:38:28 UTC
Note: the following bug applies to GNOME as a whole, not just GConf.  Further discussion and work will no doubt be required before a suitable implementation can be decided upon.

By default GNOME creates a number of different configuration files and directories in a user's $HOME directory.  I count at least the following:

Files: .dmrc .gtk-bookmarks
Directories: .config .gconf .gconfd .gnome2 .gnome2_private .gstreamer-0.10 .gvfs .nautilus

Future versions of GNOME should store ALL configuration settings in a single directory (e.g. $HOME/.config).  This is in line with the longer-term goals of the freedesktop.org config specification (http://www.freedesktop.org/wiki/Specifications/config-spec).

I can see the following benefits to moving towards a single config directory:

- makes backup/restore more straightforward
- improved security (e.g. chmod 0700 $HOME/.config)
- allows users to use version control on their config files
- remove unnecessary clutter from $HOME
Comment 1 Martin Meyer 2008-04-14 23:57:33 UTC
This is a dup of Bug 523057 I think.
Comment 2 Christian Persch 2009-03-01 19:03:08 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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