Re: panel gconf changes

[Jonathan Blandford <jrb redhat com>]

"Kevin Vandersloot" <kfv101 psu edu> writes:

> Hi Mark. Shouldn't gconf handle this properly on make install, instead of
> requiring the user to delete schemas files manually? It would seem insane that
> every time a schemas file is changed, the user has to delete the old one.

The panel can't and shouldn't handle fixing old keys on make install.
What instead has to happen is for the panel to be able to support old
keys.  I don't think it's unreasonable for us to require people to blow
away their keys between Betas, and let people know that there will be
some gconf churn during the devel cycle.  However, we do need to make
sure that we always have an upgrade path from stable release to stable
release.  As soon as 2.0 is out I'm planning on making a CHANGES file in
libgnome/schemas so we can track changes internally[1], and better write
an upgrade script when 2.2 rolls around (if needed).

Thanks,
-Jonathan


[1] No changes are planned for the 2.0.  This is more for 2.2,