> In this mail, I am saying the downloadable application package(Tizen native package(*.tpk)
> or Tizen web package(*.wgt)) not the rpm packages.
>
> In tizen ecosystem and tizen store, application developers can register thier apps that are packaged by tpk or wgt only.
> I don't want to re-invent the existing rpm packagement system, the feature is just related to downloadable application
> packages like apk in Android.
To be clarified, rpm or deb packaging system is perfect for platform with many sub-libraries. In this case, the dependency handling is of great concern and current modern packaging system does everything needed. In this environment, applications like thunderbird or libreoffice is treated as one of the package provider.
However, unlink traditional unix/linux model, app environment is different. All of the platforms provide a kind of abstraction layer to the underlying system and the packaging format (apk or tpk) is just a container for the contents. Actual dependency or capability is handled by the inside contents in the form of manifest file and not by the packaging format itself.
There was no issue so far when handling the app itself. What Mr. Ham suggested is about library to be shared and now we are on the boundary between two of above. Ham's proposal is to give app or platform the full controllability over dependency and not the packaging format.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
