Quote:
Originally Posted by kido.resuri
I missed that thread(s) discussing affiliates, but maybe I'll do a search on it. I just tested for Beta and Kobo, so don't know the others.
Anyway, there are actually 3 possible UpgradeTypes.
1 - Let's the user decide to update or skip it, and there is an option to view the release notes. If the user accepts the update, it will act as UpgradeRequired type.
2 - (UpgradeRequired) This type downloads and "prepares" the update (by unziping it), and lets the user decide to install it now or later. If the user selects later, then the update is done upon next boot. (KoboRoot.tgz sits in .kobo untill next restart.)
3 - (UpgradeForced) This type will download, prepare and install the update without asking the user. The install is done by a reboot, I guess the usual way, but without user interactions.
|
I don't think Kobo use type 1 any more. I think they stopped using when they changed to the tiled home page. Type 2 is what they usually, and I don't think I have seen type 3. Except that that is what effectively is done if the update is found during the daily auto-sync.
Quote:
|
So if KSM is set to handle the updates, then nickel's update shouldn't bypass this mechanism, even with forced upgrade.
|
I'm not sure what you mean by that. If KSM is handling the update, then nickel won't get a chance to do anything with them.