Re: [Evolution-hackers] Upgrade path fix

On Tue, 2003-11-18 at 09:02, Ettore Perazzoli wrote:

right now components upgrade from an existing Evolution version when
they are first activated.  However, that's bad since they get all
activated at the same time and it's not clear to the shell when that
happens (so e.g. if there are progress dialogs they'll interfere and

So I have added a upgradeFromVersion() method in Evolution-Component.idl
that you are now supposed to implement for your component to upgrade the
configuration settings.  If you don't implement that method, the shell
won't complain -- but you should.

So we should move all the migration stuff into this method.

Please let me know if this method is not enough for your component's
needs so we can massage it more in that case.

The mechanism is similar to that of the old e-config-upgrade, i.e. it
stores the version number in a GConf key and attempts an upgrade if the
current version number is higher than the old one.
Shouldn't it be the same mechanism, not just similar?

BTW, I am not sure if we are going to be able to support upgrading from
versions older than 1.4 easily...  Maybe we can still invoke
e-config-upgrade and make it convert to 1.4 format, then run the
Either that or separate the upgrade bits and put it in each component.  It might be neater to put it in one place for each component.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]