On 03/10/2014 05:24 PM, Dominig ar Foll (Intel OTC) wrote:
Hi,
until said otherwise, I am the architect in charge of Multi User and I
will repeat for those who missed it, what I said in an earlier mail.
I do not think that the model of adding, to the module in charge of
creating new users in the system (useradd, gumd or any other), App
specific user resource creation tasks such as DB, directories, config
files, ...
Such model is an ugly hack, which will break rather earlier than later.
Application knows what resources they need in relation to a specific
user at installation as well as later during update or upgrade.
Those tasks need to stay with the Apps themselves.
Until someone convince me that I am incorrect in my statement about risk
on system stablity on the long term, I will not accept to off load these
App specific resources creation to the useradd service in Tizen.
Apps developpers, that is your job.
This is not about apps developers, but about profile developers.
The profile (or The Product) necessarily has to contain more than just
bare platform can provide. Profile developers are kind of platform
developers but they have to put up with whatever they get as a platform
and customize it based on specific requirements.
This customization part is really critical, this is what makes operating
system a platform and not a specific product.
In this specific case, if I wasn't clear enough about it, I'm not
advocating extension mechanism to solve app developers' resource
management problems (which is easily remedied as I have already admitted).
What we would like to have is to be able to extend user creation process
to do stuff that shouldn't be put in platform code but is necessary in
context of a specific profile for the user to be correctly
instantiated/cleaned up.
Best Regards,
Leonard Milcin
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
