[OE-core] Using users/groups from another recipe than the one creating them

Peter Kjellerstedt peter.kjellerstedt at axis.com
Fri May 23 10:38:10 UTC 2014


> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf Of
> Peter Kjellerstedt
> Sent: den 19 maj 2014 10:15
> To: OE Core (openembedded-core at lists.openembedded.org)
> Subject: [OE-core] Using users/groups from another recipe than the one
> creating them
> 
> Which assumption is correct: "a recipe A that depends on another
> recipe B can use users/groups that B creates" or "all recipes must
> create the users/groups they require themselves"?
> 
> The problem for us is that we have a lot of recipes that create
> users and groups, and subsequently a number of other related recipes
> that need to use those users and groups.
> 
> If the first assumption is correct then the useradd.bbclass needs to
> be corrected so that it adds a dependency from do_install to
> base-passwd:do_populate_sysroot and
> base-passwd:do_populate_sysroot_setscene, because if either of those
> tasks execute they will overwrite /etc/passwd and /etc/group,
> effectively removing any users/groups that were created earlier...
> 
> On the other hand, if it is the second assumption that is correct,
> then there should be QA tests in place to make sure all recipes
> create the users/groups they use.
> 
> //Peter

*ping* 

Doesn't anyone know how users and groups are supposed to work?

//Peter




More information about the Openembedded-core mailing list