i kind of think that it's not worth chasing. 1 app == 1 package. that is all upgraded/installed/uninstalled together. it CAN indstall multiple binaries (multiple executables and thus icons to launch - this one package. it could also installl just data files or shared libs or something else with no binaries at all).
as long as: 1. apps can be installed in $HOME as a user id by that user id with no special root permissions we're fine. 2. apps live entirely within their directory - any symlinks to data outside an app dir is managed by tools outside of the app itself (catch - i might point at freedesktop.org for where to put cache and config files like ~/.cache and ~/.config - but a bit late for that now - i'd also have just suggested we have .desktop files... but anyway - ignore this). 3. app install dirs can be moved anywhere in the filesystem and the app must continue to work (if launched again there). i think this should be sufficient. for now at least. hybrid aps will just have to update both ends at the same time. On 05/06/2015 03:19 PM, sangyoon jang wrote: > > Hi, > > > > I want to talk about old discussion about tizen application directory > layout. > > As we said, the current (Tizen 3.0) directory layout is different with > Tizen 2.x. > > (And I found that the app-installer cannot install multi-app package > as well) > > Since we are not prepared to change directory layout, I think we > should follow Tizen 2.x 's, for now. > > (for the compatibility also) > > > > Now the many things are changed (security policy, the installer, ... > etc) and the 3.0 SDK is not release yet(packages are generated by SDK), > > so i think we need to discuss and clarify whether to change the > application package directory layout policy. > > > > > > Regards, > > Sangyoon Jang > > > > > > ------- *Original Message* ------- > > *Sender* : Rafal Krypa<[email protected]> Senior Software > Engineer/SRPOL-Security (TP)/삼성전자 > > *Date* : 2015-04-09 20:28 (GMT+09:00) > > *Title* : Re: About multi-app packaging directory policy > > > > On 2015-04-08 05:59, sangyoon jang wrote: >> Dear folks, >> >> It seems that the multi-app packaging directory policy is different with >> Tizen 2.3 >> According to 2.3 SDK, a sample multi-app package's directory hirearchy is >> like this: >> >> . >> ├── author-signature.xml >> ├── bin >> │ └── mainapp >> │ └── subapp >> ├── lib >> ├── res >> ├── setting >> ├── shared >> │ ├── data >> │ ├── res >> │ │ └── mainapp.png >> │ │ └── subapp.png >> │ └── trusted >> ├── signature1.xml >> └── tizen-manifest.xml >> (pkgid:org.tizen.mainapp, main appid:org.tizen.mainapp, sub >> appid:org.tizen.subapp) >> Two applications are packaged in same root directory. > > When designing application path structures for Tizen 3.0, we couldn't > find any documents on that issue for Tizen 2.x. Is the above layout > documented somewhere or is it just common practice in 2.3? > >> But currently, app-installer(also security-manager treat as same) >> will install this package at: $HOME/apps_rw/<pkgid>/<appid>/... >>> $HOME/apps_rw/org.tizen.mainapp/org.tizen.mainapp/bin/mainapp >>> $HOME/apps_rw/org.tizen.mainapp/org.tizen.mainapp/bin/subapp > > The above path layout was introduced to support the following features: > > 1. Allow apps inside a package to be installed, uninstalled and > upgraded separately. The desire to do that was actually based on > how hybrid applications worked in Tizen 2.x with WRT+OSP (two > separate apps with the same pkgId, installed by separate installers). > 2. Isolate packages between each other by different Smack labels > (directory TZ_USER_APP/PKG_ID has distinct Smack label assigned to > package) > 3. Give applications sharing the package a place to share data > (applications have full access to package label and can write to > TZ_USER_APP/PKG_ID) > > > Features 2 and 3 can be easily supported by both directory layouts > (the 2.3 one you mentioned and the 3.0 layout). However one may expect > issues with feature 1 in the 2.3 layout model. For example what should > happen if two applications in a package provide the same file? > >> Does anybody know whether the application directory policy is changed? >> I think that the application directory policy is not consistent now. > > The path layout for Tizen 3 was designed without knowing requirements > from Tizen 2.3. We should reconsider it now if there is anything in > Tizen 2.3 that relies on the old path layout. > But it would be very beneficial to have understanding of how multi-app > packages are going to look like. What will be their life-cycle > (development, installation, upgrade). And whether or not wewant to > support appliactions that are installed separately, but come with the > same package id. > > > > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev -- The above message is intended solely for the named addressee and may contain trade secret, industrial technology or privileged and confidential information otherwise protected under applicable law including the Unfair Competition Prevention and Trade Secret Protection Act. Any unauthorized dissemination, distribution, copying or use of the information contained in this communication is strictly prohibited. If you have received this communication in error, please notify the sender by email and delete this communication immediately.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
