Hi all, Corentin asked last week how a multi applications package is packaged.
There is no clear documentation on this point. At this time we know only this : -> manifest files mentions each app by using either app-svc tag or app-ui depending of the subtype of the app. -> each applications should be stored in a proper directory. as Corentin mentioned ( and as indicate in the wiki https://wiki.tizen.org/wiki/Application_framework#File_Applications_Full_Paths ) /home/<user>/apps_rw/<pkg_id>/app1_name/manifest.xml /home/<user>/apps_rw/<pkg_id>/app1_name/icon.png /home/<user>/apps_rw/<pkg_id>/app1_name/... /home/<user>/apps_rw/<pkg_id>/app1_name/manifest.xml /home/<user>/apps_rw/<pkg_id>/app1_name/icon.png /home/<user>/apps_rw/<pkg_id>/app1_name/... Currently, most of the existing packages contains only 1 applicaitions. In the package archive there is no specific hierachy directory at root path we have the application files. ./manifest.xml ./icon.jpg .... So to install a package with only 1 application we need to create the pkg_id path and application name directory to be compatible with the existing packages But to install a package with multiple applications we need to be sure to have either a consistent hierarchy inside the archive. (1) ./manifest.xml ./app_name1/app_1_binary ./app_name2/app_2_binary ./app_name3/app_3_binary .... or a new sub tag that indicate wich files are associated to an application inside the manifest...(2) In my opinion, I'm not sure introducing a new tag inside a manifest is a good idea, it make packaging a little bit more difficult. Check if the file hierarchy is aligned with the manifest is easier to implement and keep the packaging simple. Indeed if we choose the option 1 then we have to create only one directory that correspond to pkg_id path. Dominig, Pawel could you share your point of view? Thanks in advance BR & Happy new year! Baptiste -- Baptiste DURAND Eurogiciel Vannes/FR
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
