Re: gconf_engine_remove_dir and gconf_engine_remove_all_entries

[Colm Smyth <Colm Smyth ireland sun com>]

Oops, remove_all_entries does not exist yet (except in the Berkeley DB
backend), but I believe we need it in addition to remove_dir;
the difference would be that remove_all_entries removes entries
(keys) from a given directory while remove_dir is a recursive
delete of directories and keys.

I've written gconf_engine_remove_dir() and prepared the code for
gconf_engine_remove_all_entries(); naturally the latter isn't much
use without a corresponding implementation in the backends.
Havoc, Ben, what do you think?

Colm.

>From: Colm Smyth <colms ireland sun com>
>Subject: gconf_engine_remove_dir and gconf_engine_remove_all_entries
>To: gconf-list gnome org
>Mime-Version: 1.0
>Content-MD5: jAKR2TDCIv1WPJLPNfYnxQ==
>
>Hi,
>
>Although the backends and gconf-sources code exists to offer
>a remove_dir and remove_all_entries API, the code to make
>these available is incomplete. The CORBA stubs for remove_dir
>are there, but that's it.
>
>I'll write and putback the code for gconf_engine_remove_dir
>along with my changes to support scoping and subsetting of databases,
>but it would be fantastic if someone else would write the
>client-side code and the CORBA code for remove_all_entries.
>
>Colm.