Restoring applications after flashing: enable “maemo Extras” first.

Sunday, 2. Dec 2007

You might have noticed that OS2008 can now backup and restore the names of the packages that you have installed. The Application Manager can take that list and install them all at once. The catalogue configuration of the Application Manager is also backed up and restored, of course.

There is one (small?) snag, though: the pre-configured catalogues are not backed up. This seems to be the right thing to do since we can assume that the new image has a better idea of what the pre-configured catalogues should be than the backup. Unfortunately, the maemo Extras catalogue is pre-configured as “disabled”, and thus, since it is not included in a backup, you always have to enable it explicitly after flashing.

Let me say that again: after flashing, you need to enable the maemo Extras catalogue before being able to restore packages from it. Unfortunately, the first-boot procedure doesn’t give you the opportunity to do this. What will probably work quite well is to perform the restore on first-boot to get all your settings back, but to not accept the offer to install the applications right now. Then open the Application Manager manually, enable the maemo Extras catalogue, and select “Tools > Restore applications…”.

That’s an accident, of course, it’s not by design. Sorry for that. We’ll figure out something for the next release. The easiest thing is to just include the “maemo Extras” repository in the backup, I guess. But then again, why not include all pre-configured catalgues? What do you think?


3 Responses to “Restoring applications after flashing: enable “maemo Extras” first.”

  1. jSmith said

    I’m really thinking that updater should be able to update OS without having all these headaches.Just like “full featured” desktop Linuxes do.IMHO flashing should be LAST resort when system is really completely trashed.

  2. Juha said

    I think you should just back up a boolean “Extras enabled yes/no” and let application manager map it to the current extras repository (if any). I agree it might not be very clean design to special-case one repository like this, but if a future version needs something else, it could just ignore the setting or pop up a dialog when started.

  3. Or, given that between releases the “maemo Extras” (horrible capitalisation, BTW ;-)) repository URL may change; how about storing in the backup the *names* of the enabled repositories?

    This has two benefits:

    1) If the user has enabled “maemo Extras”, it’ll be automatically re-enabled.
    2) If the user has disabled some of their added repositories, this information will also be restored.

    (2) may already happen, I’ve not yet tested it. But it sounds like the right solution to (1), to me.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: