[Dev] 3rd party so library installation feature
c.haitzler at samsung.com
Tue Oct 15 12:14:52 GMT 2013
awesome. you just re-invented rpm... :)
On 10/15/2013 09:10 PM, 함동읍 wrote:
> Dear All,
> I want to discuss "3rd party so library installation feature.
> 1. To provide a way to download a necessary shared library from authorized/dedicated site
> 2. If users want to use application B which uses a shared library, they download that library from the site by themselves.
> 3. When another application C requires the same library later, users can use it without additional download.
> 4. When the end user tries to remove application B owning the shared library that is required for other installed applications, the platform should warn the user that designated applications would not work correctly if the library is removed.
> 5. The platform should provide a naming service for the installed shared library so that any 3rd party application using it may locate and use (load) it without knowing the specific id of the owning package/application.
> 1. Library provider
> 1) Tizen app can be a library provider with specifying a tag and embedding the libraries.
> 2) Library provider specifies a tag in the manifest file.
> a) <ProvideLibrary>http://tizen.org/library/name</ProvideLibrary>
> b) This tag can be restricted to partner and platform privilege levels.
> 3) Libraries are located at /shared/res/ to share with other apps.
> 2. Library user
> 1) Library user specifies a tag in the manifest file.
> a) <RequireLibrary>http://tizen.org/feature/library/name</RequireLibrary>
> 2) Library user has to check whether the library provider app has been installed or not.
> a) The library provider app is not installed, request of installation is sent to Store client.
> 3. Platform package manager
> 1) Installed apps from Store should be uninstalled anytime when device user requests through the System settings.
> a) Library provider app should be uninstalled anytime.
> b) Deep relationship with library provider app and library user is not recommended.
> Library user app can be working without library provider app, if needed.
> 2) Package manager can extract information of provider and users using manifest at installation time.
> a) Package manager can display a warning popup to notify a message.
> i.e. “If this app is uninstalled, [AppB, AppC and AppD] apps may not be working well.”
> b) If the provider is uninstalled, the related user apps can be terminated, if needed.
> 3) Application libraries are located in app directory and don’t be moved to common library directory.
> a) Library path is not specified in library user app.
> 4) Package Manager can support library path API using the key that is specified in manifest.xml.
> In Android, some apps use functionality and resources of another app
> 1. Several apps request functionality to an app
> 2. Several apps use an app as a service app
> 3. App accesses another app resource directly
> 4. Android supports <uses-library>, but these libraries are not downloaded by store but preloaded.
> Please check considerations and give me the feedback.
> Best regards,
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev