Re: gconf_client_recursive_unset

[Rodrigo Moya <rodrigo gnome-db org>]

On Sun, 2002-03-03 at 22:21, Havoc Pennington wrote:
> 
> Rodrigo Moya <rodrigo gnome-db org> writes:
> > 
> > I was in need of removing a GConf directory from my code, which uses
> > GConfClient, and didn't find anything apart from
> > gconf_engine_recursive_unset.
> > 
> > So, here's a patch that adds gconf_client_recursive_unset function. Just
> > tested for my particular case, and it worked perfectly.
> > 
> > Also, I've added gconf-sources.h to the list of header files to install,
> > since GConfUnsetFlags is defined there, and is needed by the new
> > prototype in gconf-client.h
> > 
> > Can I commit?
> > 
> 
> This breaks the API freeze. For now you have to call all_entries then
> call _unset on each entry. Or you could g_spawn ("gconftool-2
> --unset-recursive /foo") perhaps.
> 
:-( the API freeze. Well, I'l, do one of the solutions you propose while
waiting for the patch to be applied.

> When we do add this function publicly UnsetFlags should be moved,
> rather than installing gconf-sources.h - gconf-sources.h is a private
> header with a bunch of private stuff in it.
>
ok, keep me informed when that function can be added, and I'll work that
out.
 
> Thanks for the patch though, it's certainly planned post-GNOME-2. If
> you want to open a bugzilla bug and attach the patch that'd be
> appreciated.
> 
http://bugzilla.gnome.org/show_bug.cgi?id=73323

cheers
-- 
Rodrigo Moya <rodrigo gnome-db org> - <rodrigo ximian com>
http://www.gnome-db.org/ - http://www.ximian.com/