Here is a design proposal for altering the installed layout of application bundles to be suitable for upgrade/rollback, data-reset, containerization, and the theme installation use-cases raised by Ramya and Suma on https://bugs.apertis.org/show_bug.cgi?id=575:
https://wiki.apertis.org/Application_Layout
Please let me know if there are any requirements that are not covered, or areas that are unclear or unsuitable.
There are some unresolved questions about the requirements, for which I would particularly appreciate feedback:
https://wiki.apertis.org/Application_Layout#Unresolved_design_questions
The part discussing icon themes should eventually be split out into a separate design document that specifically covers what has been said on https://bugs.apertis.org/show_bug.cgi?id=575, but for the moment it's just a subsection of Application_Layout.
Thanks, S
Hello Simon,
Can you explain what is meant by data reset in the point below?
"Does data reset uninstall apps? Does a data reset leave the installed store apps installed, or does it uninstall them all? (In other words, does it leave store apps' static files intact, or does it delete them?)"
Can you give me a usecase where data reset is done?
Best regards
Suma L RBEI/ECF
Tel. +91(80)6657-4464
-----Original Message----- From: Devel [mailto:devel-bounces@lists.apertis.org] On Behalf Of Simon McVittie Sent: Wednesday, November 18, 2015 11:59 PM To: devel@lists.apertis.org Subject: [Devel] Application Layout design proposal
Here is a design proposal for altering the installed layout of application bundles to be suitable for upgrade/rollback, data-reset, containerization, and the theme installation use-cases raised by Ramya and Suma on https://bugs.apertis.org/show_bug.cgi?id=575:
https://wiki.apertis.org/Application_Layout
Please let me know if there are any requirements that are not covered, or areas that are unclear or unsuitable.
There are some unresolved questions about the requirements, for which I would particularly appreciate feedback:
https://wiki.apertis.org/Application_Layout#Unresolved_design_questions
The part discussing icon themes should eventually be split out into a separate design document that specifically covers what has been said on https://bugs.apertis.org/show_bug.cgi?id=575, but for the moment it's just a subsection of Application_Layout.
Thanks, S
On 23/11/15 12:27, Suma Shanbhog (RBEI/ECF4) wrote:
Can you explain what is meant by data reset in the point below?
It's our equivalent of the "factory reset" in mobile OSs, for instance "Settings -> Backup & Reset -> Factory data reset" in Android 5. I was told this is a requirement I need to consider for this and related designs.
Can you give me a usecase where data reset is done?
I believe the use case is something like this: I own a car that is based on Apertis, drive it for a while, and then sell it. Before selling the car, I want to remove my personal data. After the data reset, the Apertis environment should be in the same state as if I had taken an unused car of the same specification, brought it up to date, and not done anything else.
The same mechanism might be useful for a related use-case: a car rental company has some cars based on Apertis in their fleet. When each car is returned after use, they perform a data reset to return the rental car to a "clean slate" state for the next driver, with all preferences returned to defaults.
I think these might mean we want most app-bundles to be deleted by the data-reset (otherwise the new owner could tell a lot about me by observing the set of installed apps), but we want to be able to flag a subset of app-bundles that will stay?
In the "sell my car" use-case, we'd want to keep the preinstalled app-bundles, perhaps any new app-bundles that were installed automatically by OS updates, and perhaps any app-bundles whose licensing is linked to the car rather than my store account.
In the "rental car" use-case, the rental company might install a store app-bundle which adds their return locations as POI, which they'd want to keep across a reset.
Thanks for clarifying. Yes, this needs to be considered.
In my opinion it makes sense to remove the store apps and leave the native apps. This apart from user data. However, I think there are some words said about it in system update concept. Where does this actually fit in? App layout or system update?
Best regards
Suma L RBEI/ECF
Tel. +91(80)6657-4464
-----Original Message----- From: Simon McVittie [mailto:simon.mcvittie@collabora.co.uk] Sent: Monday, November 23, 2015 7:35 PM To: devel@lists.apertis.org Cc: Suma Shanbhog (RBEI/ECF4) Subject: Re: [Devel] Application Layout design proposal
On 23/11/15 12:27, Suma Shanbhog (RBEI/ECF4) wrote:
Can you explain what is meant by data reset in the point below?
It's our equivalent of the "factory reset" in mobile OSs, for instance "Settings -> Backup & Reset -> Factory data reset" in Android 5. I was told this is a requirement I need to consider for this and related designs.
Can you give me a usecase where data reset is done?
I believe the use case is something like this: I own a car that is based on Apertis, drive it for a while, and then sell it. Before selling the car, I want to remove my personal data. After the data reset, the Apertis environment should be in the same state as if I had taken an unused car of the same specification, brought it up to date, and not done anything else.
The same mechanism might be useful for a related use-case: a car rental company has some cars based on Apertis in their fleet. When each car is returned after use, they perform a data reset to return the rental car to a "clean slate" state for the next driver, with all preferences returned to defaults.
I think these might mean we want most app-bundles to be deleted by the data-reset (otherwise the new owner could tell a lot about me by observing the set of installed apps), but we want to be able to flag a subset of app-bundles that will stay?
In the "sell my car" use-case, we'd want to keep the preinstalled app-bundles, perhaps any new app-bundles that were installed automatically by OS updates, and perhaps any app-bundles whose licensing is linked to the car rather than my store account.
In the "rental car" use-case, the rental company might install a store app-bundle which adds their return locations as POI, which they'd want to keep across a reset.
On 24/11/15 08:05, Suma Shanbhog (RBEI/ECF4) wrote:
In my opinion it makes sense to remove the store apps and leave the native apps. This apart from user data.
We can't remove built-in apps anyway, because they're built-in to the platform image.
That would result in preinstalled store apps (see the Applications design document for the difference) being lost in a data reset?
However, I think there are some words said about it in system update concept. Where does this actually fit in? App layout or system update?
"Yes" :-)
The app layout proposal is really a plan to enable several orthogonal features, rather than being a new feature in its own right. Most of the requirements stated on the wiki page are re-stating/clarifying things that are already required by the Applications, System Update & Rollback or Preferences & Persistence designs.
The reasons I've written it up as its own document are that we need to make sure the same filesystem layout satisfies the requirements of all of those design documents, and that the concept design documents aren't really specific enough about the filesystem layout to guide implementations.
-
Simon McVittie -
Suma Shanbhog (RBEI/ECF4)