Hello Young, Yes, this deserves some clarifications.
The two packages tizen-platform-config and tizen-platform-wrapper do not create any directory. Instead, they provide the paths for directories, through different mechanisms (bash variables definitions, RPM macros, shared library to solve paths at run time ...)
In the case of default-files-tizen, this is a package that should be modified to create some base directories using the definitions contained in tizen-platform-config (ex: replace /opt/home by %TZ_SYS_HOME)
Also, the 'app' user should be created using useradd in postinstall script instead of creating the home dir /opt/home/app in the default-files-tizen rpm.
Kind regards, -- Stéphane Desneux Intel OTC - Vannes/FR On 08/12/2013 09:52, Young Ik Cho wrote:
2013/12/3 Stéphane Desneux <[email protected] <mailto:[email protected]>> To start the migration of 200+ packages to multiuser architecture, we introduced two new packages: tizen-platform-config and tizen-platform-wrapper. The main package is tizen-platform-config and contains the definitions for variables to be used in a given profile. Actually, these variables are mostly used to replace hardcoded paths in source code or spec files, but their usage could be wider in the future. Could you clarify the difference between platform/core/base/default-files-tizen and these two packages? So far, default-files-tizen package organized default directories like /opt/home/app, /opt/home/developer or /opt/home/root directory and it seems to me that new packages may provide similar information. Young
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
