Reid Ellis wrote: > Ideally, Chandler would check for updates, and when it finds there is one: > * ask the user if they want to upgrade > * if so, the new Chandler is downloaded > * data is backed up > * the new Chandler launched with flags(?) to load the backed-up data.
That works fine if the user is managing the Chandler installation manually. However, that won't work for packaged distributions once Chandler goes into the repostories and users install it with a package manager. There won't be upgrade check in a packaged application, because the upgrade is handled by the package management system. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
