On 03/09/2014 11:37 PM, Dominig ar Foll (Intel OTC) wrote:
Hello;
like Auke, I hate the idea to add more script because it could easy lock
the system.
I have describe why I feel that it's an idea which is dangerous and
should not be entertained.
(...)
We need to be able to guarantee that a user addition cannot be
potentially failed by any applications. In order to acheive that, we
need to leave to the application the responsibility to add the missing
user DBs, config, directories, ... at the first run.
Hello,
for a simple situations where just a resource is needed we should advise
to do as you propose, ie. if (!db_exists()) create_db();
At the same time, though, we should think about platform needs, where we
don't and can't know about all possible uses. It then makes sense to
have at least some extension points so that we don't have to change user
management code for each different profile and then cope with
forever-lingering patches. The specific part could be supplied by
profile-specific package with the core user management code stable and
hopefully unchanged.
For example, some guys here work on having, possibly, per-user
containers. It makes sense to extend user creation process to
spawn/configure these users' containers at the moment of user creation.
The user is never actually completed without container so it is not a
case for if (!container_exists()) create_container();
Regards,
Leonard Milcin
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
