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

[Martin Jansa]

On Mon, Jun 09, 2014 at 03:39:46PM +0200, Peter Kjellerstedt wrote:
> > -----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 23 maj 2014 12:38
> > To: OE Core (openembedded-core at lists.openembedded.org)
> > Subject: Re: [OE-core] Using users/groups from another recipe than the
> > one creating them
> > 
> > > -----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
> 
> *ping again*
> 
> Well, this is somewhat discouraging. Three weeks and not a single 
> response. Are we really the only ones that care about users and 
> groups and how they are created? Doesn't anyone know which of my 
> two assumptions above are correct?
> 
> Personally I would prefer that all recipes create the users and 
> groups they require themselves as this keeps them more self 
> contained. I have no idea how to write a QA test to verify this, 
> but I assume it should be possible...

My experience from Dylan release is that only users/groups created in
base-passwd work reliably, with useradd.bbclass we were seeing random
files getting random user/group owners (comparing buildhistory report
files-in-image.txt from multiple builds which weren't using sstate).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20140609/57d1c7bf/attachment-0002.sig>