Hi all

Here is the status of the Work shop about App_installer package

confcall 20th of November
Present : Pawel Sikorski , Dominique Le Foll, Baptiste Durand


------------------------------
------------------------------------------------------------------------------------------
Business logic location :

A decision has been taken to re localize the business logic in the
frontend, that means installer backend should not have a specific logic.

In consequences, the backend installation should be able to execute a
request ( install / uninstall / reinstall / update a package)

That means if an installation fails because the package is already
installed an exception should be thrown by backend, there won't no implicit
update.


------------------------------
------------------------------------------------------------------------------------------
List of step for installation :

Here the list for an app installation
1) Unpack archive

2) Signature step
2a)signature validation
 2b) certificate check
2c) Extraction of level of signature (Platdorm/ Partner ...)

3) Extration of manifest
3a) Extraction of privileges and comparison with signature level

4) Creation of final Directory + Cpopy of Applciation files
5) Generate final manifest.xml + Generate desktop File
6) Register applications in database.
7) Security manager calls for Set smack Label


Samsung  Poland team is in charge to  find how the steps 2a/b/c & 3a should
be handled.
(Security Manager could be a candidate to do this check)

------------------------------------------------------------------------------------------------------------------------------
Other mode of Installation

It was concluded that for now only Offline Installation is relevant.
Offline installation should be handled by a dedicated set of steps.


The wiki will be updated following this.


BR


-- 
Baptiste DURAND
Eurogiciel Vannes/FR
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to