From 4100889de3d01def08e3bf7dfee23b7741d2c0cd Mon Sep 17 00:00:00 2001 From: adamw Date: Sat, 12 Apr 2003 02:34:27 +0000 Subject: Detailed description of gconf. git-svn-id: svn://creme-brulee.marcuscom.com/ports/trunk@581 df743ca5-7f9a-e211-a948-0013205c9059 --- devel/gconf2/pkg-descr | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) (limited to 'devel/gconf2') diff --git a/devel/gconf2/pkg-descr b/devel/gconf2/pkg-descr index c4f8b27a2..0658ef70f 100644 --- a/devel/gconf2/pkg-descr +++ b/devel/gconf2/pkg-descr @@ -1,4 +1,22 @@ -GConf is a configuration database system for the GNOME desktop, -functionally similar to the Windows registry but lots better :-) +GConf attempts to leapfrog the registry concept. It's a library which provides +a simple configuration data storage interface to applications, and also an +architecture that tries to make things easy for system administrators. + +Here are some of the features of GConf: + + * Replaceable backend architecture. + + * Configuration key documentation. Applications can install documentation + along with their configuration data, explaining the possible settings and + the effect of each configuration key. + + * Data change notification service. If configuration data is changed, all + interested applications are notified. The notification service works + across the network, affecting all login sessions for a single user. + + * The client API is very abstract. + + * GConf does proper locking so that the configuration data doesn't get + corrupted when multiple applications try to use it. WWW: http://www.gnome.org/projects/gconf/ -- cgit v1.2.3