Re: [GnomeMeeting-devel-list] 1.00 Freeze

[Miguel Rodríguez <migrax terra es>]

El mar, 27-01-2004 a las 11:25, PUYDT Julien escribió:
> On mar, 2004-01-27 at 11:17, Damien Sandras wrote:
> 
> > That code audit is part of the fix, but that is just another protection.
> > It happens frequently that gconf_test_age is correct, but other keys are
> > not.
> 
> I propose (post 1.00) to get rid of that gconf_test_age, and check the
> return result from gconf everytime. That is much more robust, and is the
> right fix.
Both are compatible. gconf_test_age is/was great to warn people that
their installation was broken. Those were difficult times when nobody
managed to properly setup gconf. Don't know if it still relevant, but as
a warning to the user is useful.
Problem is that it has prevented developers to protect gm against broken
settings. Gconf comes with utilities to test programs against this.
Maybe they should be used whenever a gconf setting is added/changed.

To sum up:
gconf_test_age: Great for users. Gives an explanation and lets them fix
major problems.
test every time: A must.
test at startup: longer startup time. not 100% robust. Maybe as an
interim measure, but not the real fix.
> 
> Snark
> 
> _______________________________________________
> Gnomemeeting-devel-list mailing list
> Gnomemeeting-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list