On Sun, Feb 28, 2010 at 12:56 PM, sam tygier <[email protected]> wrote:
> Tom Hacohen wrote: > >> Hey, >> >> Opimd got rewritten according to the guidlines in this page: >> http://wiki.openmoko.org/wiki/Opimd_redesign . New opimd is faster, >> "smarter" and easier to handle, so we want to more it as soon as possible, >> for both your sake and ours. I have been using it for >> a couple of weeks now (I'm not the only one) and it works great and bug >> free so there really is no reason why not to move. >> >> The only "problem" is that new opimd has a different db design than the >> old one, and therefore, you need to convert your database to the new format. >> The database conversion takes a lot of time, so we have to think carefully >> when we want to do it. There are 3 main possibilities: >> >> 1. Opkg postinst (will do it automatically when you upgrade opimd) - >> >> Means a simple upgrade may take hours. >> 2. First run after the installation - (Again, takes a lot of time, >> but ok) >> 3. When ever you want to, just add a nice message in opkg. - The >> >> script converts databases, it doesn't import so you will loose all >> changes done between installation and the convert. >> >> I prefer the second, because it's cleaner than the others. >> >> Very important note: new opimd does not support backends at all, if you >> want anything that's not it's internal db, just import using pisi, this is >> the price you have to pay for a working, solid and fast opimd. >> >> Cherrs, >> -- >> Tom. >> >> > > can the conversion process handle interruption. not necessarily to pick up > where it left off, but to try again. that way it could be triggered in the > post install, but if the user turns the phone off it will be triggered again > at first run. > > sam > _______________________________________________ > It can handle interruption, you can just stop it whenever you want (though you'll have to start from scratch if you stop it). So maybe a good idea would be doing both 1 and 2 (and of course if already converted it won't start again). -- Tom.
_______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
